< said:
> This is similar to the way most VxWorks network drivers operate:
Right -- in fact, as I recall, Mogul's paper mentions that his
solution is very similar to the way many RTOSes operate.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the
> it occurs to me that there is a potential infinite loop in
> most if not all ethernet drivers. Basically, on a
> receive interrupt, such drivers loop around the status word
> until the receive queue is drained.
>
> If the body of the loop takes approx the same as
> the packet interarrival time,
Garrett Wollman wrote:
>
> < said:
>
> > it occurs to me that there is a potential infinite loop in
> > most if not all ethernet drivers. Basically, on a
> > receive interrupt, such drivers loop around the status word
> > until the receive queue is drained.
>
> One possible right way to deal wi
Mark Peek wrote:
>
> At 9:09 PM -0500 2/8/01, Garrett Wollman wrote:
> >One possible right way to deal with this is to get rid of the
> >two-level interrupt scheme (for fast interfaces at least) and push the
> >packets all the way through the network stack. This will ensure that
> >if packets ar
At 9:09 PM -0500 2/8/01, Garrett Wollman wrote:
>One possible right way to deal with this is to get rid of the
>two-level interrupt scheme (for fast interfaces at least) and push the
>packets all the way through the network stack. This will ensure that
>if packets are arriving faster than we can
