I'm not sure what "time based scheduling" is, so I don't know if what
I described is or isn't that.
What I was trying to describe is a minimalistic approach to real-time
system design, inspired in part by the evil experience of using more
complicated schemes that sounded good but didn't work well.
The system I've settled on as most desirable -- which is what I'm
using at the moment -- is a single priority design, with all tasks
running to completion (or explicit reschedule), and no interrupts,
just I/O polling.
So it isn't scheduling in terms of deadlines or other time based
notions, but rather just round robin scheduling of active tasks. So
long as you know the time bounds it's trivial to analyze, and even if
you don't know hard time bounds, you still obviously have guaranteed
progress on all tasks. For networking boxes (which is what we do) it
turns out guaranteed liveness is what you look for; trying to come up
with hard time bounds as you might do in a process control environment
is usually more effort than it's worth.
paul
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
