On Wed, 2 Jun 1999, maryam moghaddas wrote:
> But what about RTlinux is running a realtime task, would the RTLinux kernel
> except the Network interrupt at that time? or in another word does RTLinux
> deals with the networking interrupts as a HARD realtime interrupt?
This is a matter of priorities and whether r_cli() is called in your realtime
task. Normal networking interrupts belonging to standard driver will not be
accepted at that time, but not lost as well - just delayed. But if you write
your own network card interrupt handler, you can register it with RT layer
and then it may be called. You just have very limited access to kernel
services from such real time interrupt handler.
BTW. In my opinion there is no such think like "real time kernel module". It
is the context in which a given code is executing, which decides whether it
is real time or not. You should think in this way: If I have registered some
function(s) in my code to be run when the rest of the kernel thinks interrupt
are disabled, they are real time code.
--
Tomek
--- [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/
