Every component that uses the scheduler is an active object. So a node is an active object. Or in other words scheduler maintains a prority queue of various AOs and schedules various active objects from that priority queue. Each active object in its implementation adds / removes itself to scheduler queue. Implementations can also set priorities for active objects. Scheduler does not interrupt an AO but it does take into account priorities of AOs while scheduling. Scheduler does follow FIFO among AOs that have the same priority.
On Jan 22, 7:07 am, jerand <[email protected]> wrote: > from the earlier replies, I understand that the scheduler relinquishes > control on completing its task. i would like to know how different > nodes that get attached are categorized within the scheduler. > > 1. For instance, certain nodes which give data to sink nodes have to > processed first to avoid > starvation while others need to be scheduled more frequently to > take data from a buffer/ network > so on. So based on this can you explain how different nodes get > attached to the scheduler ? > > 2 .Is there a way to prioritize my task nodes attached with the > scheduler ? > > 3. Does the scheduler follow FIFO policy ? > > 4. Is there a limitation on the number of task nodes that can be > attached with the scheduler ? > > 5. if am using seperate threads instead using of PV scheduler, what > priority should I give for the same ? What are the effects on using > the same priority as that of scheduler thread ? > > 6. Where can i find the scheduler code ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
