Tomasz Motylewski wrote:
> No. The networking and hardware drivers are of the high priority - they are
> in the kernel. RT layer was invented to put something even at higher priority
> then the kernel, which disables interrupts from time to time. If you put
> networking and HW at RT priority, then soon someone will need Real Real-Time
> Linux with additional priority layer. Memory allocation is not time bound -
> if you put all device drivers in RT, they should use pre-allocated memory.
It does not matter what is the priority level of the driver as long as they are
part
of low priority task. It means that they are higher prioritized among the low
priority task. I agree with the suggestion of Kal, all drivers should be the
part of
RT kernel, mean should be at same priority level.
> Reitarating: the more things you put at RT priority, the worse quality of RT
> you will get. RT Linux is for people who work at microseconds time scale.
> If you need responsivenes in the range of ms and networking, use other
> methods.
Mostly, I do not agree with this and probably many in this list. Theoretically
yes,
but as long as time slicing is ok with the application, there should not be
problem. Many RTOS includes lots of things. And after all it is a user who is
going to decide how to structure his/her system depending on the requirement.
Regards,
Yusuf
--- [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/
