On Fri, 17 Aug 2001, Anders Gnistrup wrote:
>
>
> Calin Culianu wrote:
>
> > Let's say your real-time thread were (erroneously) making use of some
> > kernel services that could potentially block. (Like, oh, writing to a
> > Linux fifo that might not have its buffers in memory, for instance).
> >
> > Could such cases cause the whole system to lock? Basically our real-time
> > thread is non-preemptible (not even by hardware-interrupts) so we would
> > never get out of the linux kernel routines that are blocking (since no
> > interrupts would ever make their way in to any sort of interrupt handler
> > both in RTL and in the regular kernel).
>
>
> Way are you using RTLinux for this, if it should bee non-preemptible????
> Don't you have a pthread_wait_np call or other suspend funktion???
> (every RTLinux suspend funktion will preemp the CPU (and Linux) when the
> task is ready, if it is needed.)
>
I was attempting to understand how rt-linux interacts with/preempts the
Linux Kernel, that's all. My question was more hypothetical than real. I
wanted to simply understand how/why rt-linux accomplishes it's magic.
-Calin
-- [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/
