On Mon, Nov 22, 1999 at 02:32:56PM +0530, Yusuf Motiwala wrote:
> Tomasz Motylewski wrote:
> > 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
In practice this is absolutely correct. There are 1000 microseconds in
a millisecond, the more of them that are allocated to non critical
tasks, the less are available for critical tasks. If you make everything
"realtime", then nothing is realtime.
Linux TCP/IP is a very well designed and enormously complex system. It would
be hopeless to try to recreate it at the RT level even if we ignore the
fact that TCP, which most people want to use, is fundamentally not
realtime.
> 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.
Many RTOS's include much more than RTLinux and they are slower, less
predictatable, and more difficult to maintain.
The RTLinux design paradigm puts time sliced components on the Linux side
which is optimized for time-slicing. The RTLinux side is optimized
for low latency. There is a big difference.
--- [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/
