AVR-Chat

>
>The OS itself doesn't really do polling. Obviously, supporting devices
>which don't generate interrupts would require some type of timer based
>polling.
>
>So, in an RTOS, the highest priority ready-to-run thread is always
>running. Context switches occur whenever something causes a higher
>priority blocked thread to become ready-to-run (say it's waiting on a
>semaphore and a lower priority thread signals the semaphore). The timer
>tick is used to round-robin equal priority threads.

Makes sense.

I've used round-robin and prioritized schemes.
I just sit them in the idle loop, and if I intend prioritized, then I restart from the top, otherwise, I just let it continue around.

So in the end, it's pretty much the same thing, Tasks sit and wait till they have everything they need to proceed, then they should try to exit/finish as soon as possible.


I didn't intend (or object) to this getting to be a deep discussion, I was just amused at the comparison.. 

I've wondered about using some sort of subsumption scheme, I suppose there isn't a huge difference between this and a prioritized multitasker.