[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200704060901.28628.amitkale@linsyssoft.com>
Date: Fri, 6 Apr 2007 09:01:28 +0530
From: "Amit S. Kale" <amitkale@...syssoft.com>
To: kgdb-bugreport@...ts.sourceforge.net
Cc: Herbert Xu <herbert@...dor.apana.org.au>,
Sergei Shtylyov <sshtylyov@...mvista.com>,
netdev@...r.kernel.org, jgarzik@...ox.com, mhuth@...sta.com
Subject: Re: [Kgdb-bugreport] [PATCH] 8139too: harden against TX ring overflow
On Friday 06 April 2007 07:18, Herbert Xu wrote:
> Sergei Shtylyov <sshtylyov@...mvista.com> 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 dirty
> > pointer gets out of sync); switch to using appropriate mnemonics for the
> > return values while at it.
>
> Could you please describe this netpoll scenario in more detail?
> More importantly, why wouldn't we fix netpoll instead?
We're trying to figure out a way of fixing netpoll. Don't know what the
solution is yet.
Here is what happens: in KGDB we set netpoll trapped flag. This prevents
stopping and starting of a netdev queue. Interfaces that have a small ring
(8139) run into a problem because of this. When the ring goes full, it can't
stop the queue. This doesn't make sense since in absence of ring descriptors,
the device can't transmit any more packets. Sergie had posted one more patch
last week that lets us start and stop queues in trapped state.
This patch fixes the 8139 side behavior in this context.
-Amit
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists