If you write a realtime ethernet driver, will non-rt tasks (linux user
level tasks) also use the same driver to send messages? In that case, the
QoS cant be satisfied anyway. The driver will have to be modified
significantly to include priority queues, with a best effort queue for
non-rt tasks. Take a look at a project named Rether
http://www.kashpureff.org/nic/drafts/draft-chitra-rether-00.txt
On Fri, 20 Aug 1999, Maryam Moghaddas wrote:
> Hi
> I am porting smc-ultra.c ( driver for SMC Elite16) to RTLinux, under
> kernel 2.0.36 RTLinux V1.2.
> Browsing through the news group, I found the following useful paragraph
> in MAY 99:
> " I would advice you to take a different approach - that is to make a
> critical
> part of wavelan driver real-time and call your routine directly from
> there.
> This means use request_RTirq() instead of request_irq(), use only
> pre-allocated memory buffers in the receive-transmit path, do not call
> netif_rx, process the data directly in the driver etc. In the kernel
> space
> the only difference between RT and non RT code is whether it can run at
> a
> time when the rest of the kernel thinks that interrupts are disabled. "
>
> So the same as above I replaced the interrupt request function, but
> there are some issues still vague for me.
> My impression from the email above is that I should avoid using skb
> buffers in the RTLinux interupt handler/receive/transmit path and
> inanother words discard and change them all in the code. Is this
> correct?
>
> My other question is, should I be concerened and worried at all about
> the network protocols? Should I do any changes in that regard...
>
> Thanx alot
> maryam
> --- [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/
>
--- [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/