Sergei Shtylyov wrote:
Jeff Garzik wrote:
This driver's 4-packet deep TX queue is too sensible to the
"careless" callers
ignoring its state (like netpoll in trapped mode), so add "queue
full" check at
the start of the hard_start_xmit() method (only under #ifndef
RTL8139_NDEBUG,
otherwise the
Jeff Garzik wrote:
This driver's 4-packet deep TX queue is too sensible to the
"careless" callers
ignoring its state (like netpoll in trapped mode), so add "queue
full" check at
the start of the hard_start_xmit() method (only under #ifndef
RTL8139_NDEBUG,
otherwise the queue will get stuck onc
Sergei Shtylyov wrote:
Hello, I wrote:
This driver's 4-packet deep TX queue is too sensible to the "careless"
callers
ignoring its state (like netpoll in trapped mode), so add "queue full"
check at
the start of the hard_start_xmit() method (only under #ifndef
RTL8139_NDEBUG,
otherwise the queu
Hello, I wrote:
This driver's 4-packet deep TX queue is too sensible to the "careless" callers
ignoring its state (like netpoll in trapped mode), so add "queue full" check at
the start of the hard_start_xmit() method (only under #ifndef RTL8139_NDEBUG,
otherwise the queue will get stuck once dirt
Hello.
Amit S. Kale wrote:
This driver's 4-packet deep TX queue is too sensible to the "careless"
callers ignoring its state (like netpoll in trapped mode), so add "queue
full" check at the start of the hard_start_xmit() method (only under
#ifndef RTL8139_NDEBUG, otherwise the queue will get st
On Friday 06 April 2007 07:18, Herbert Xu wrote:
> Sergei Shtylyov <[EMAIL PROTECTED]> wrote:
> > This driver's 4-packet deep TX queue is too sensible to the "careless"
> > callers ignoring its state (like netpoll in trapped mode), so add "queue
> > full" check at the start of the hard_start_xmit()