Re: potential infinite loop in network device drivers

2001-02-09 Thread Garrett Wollman
< 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

RE: potential infinite loop in network device drivers

2001-02-09 Thread Clark Jarvis
> 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,

Re: potential infinite loop in network device drivers

2001-02-09 Thread Wes Peters
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

Re: potential infinite loop in network device drivers

2001-02-08 Thread Julian Elischer
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

Re: potential infinite loop in network device drivers

2001-02-08 Thread Mark Peek
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

potential infinite loop in network device drivers

2001-02-08 Thread Garrett Wollman
< 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 with this is to get rid of the two-level int

potential infinite loop in network device drivers

2001-02-08 Thread Luigi Rizzo
Hi, 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, you migh