> X is a user space process, thus cannot disable interrupts, and
> therefore cannot block the system.

Besides, as a user process, X has absolutely no CPU bandwidth guarantees
no matter what it's priority is. The other processes heavily interfere
with timing. And ordinarily you don't have control over the processes
that the user launches on the system. If the load is high enough, I
guess it might take literally seconds before X wakes up after it has
spent its time slice. ("I guess" because I don't know the specifics of
the Linux scheduler.)


Marko

-- 
Marko Rauhamaa        [EMAIL PROTECTED]   (818) 878-6314
Sr Project Engineer   http://www.tekelec.com/      Tekelec Inc
--- [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/

Reply via email to