[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6da209ffe31744d79c1394e1f3d038db19beca51.camel@sipsolutions.net>
Date: Wed, 27 Nov 2019 09:30:51 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Alexander Lobakin <alobakin@...nk.ru>,
David Miller <davem@...emloft.net>
Cc: pabeni@...hat.com, ecree@...arflare.com,
nicholas.johnson-opensource@...look.com.au, jiri@...lanox.com,
edumazet@...gle.com, idosch@...lanox.com, petrm@...lanox.com,
sd@...asysnail.net, f.fainelli@...il.com,
jaswinder.singh@...aro.org, ilias.apalodimas@...aro.org,
linux-kernel@...r.kernel.org, emmanuel.grumbach@...el.com,
luciano.coelho@...el.com, linuxwifi@...el.com,
kvalo@...eaurora.org, netdev@...r.kernel.org,
linux-wireless@...r.kernel.org
Subject: Re: [PATCH v2 net-next] net: core: use listified Rx for GRO_NORMAL
in napi_gro_receive()
On Wed, 2019-11-27 at 10:47 +0300, Alexander Lobakin wrote:
> > Can I get some kind of fix in the next 24 hours? I want to send a
> > quick
> > follow-on pull request to Linus to deal with all of the fallout, and in
> > particular fix this regression.
>
> If Intel guys and others will agree, I'll send a patch which will add
> manual napi->rx_list flushing in iwlwifi driver in about ~2-3 hours.
Sounds fine to me.
> Anyway, this driver should get a proper NAPI in future releases to
> prevent problems like this one.
Yeah, we'll work on that, but that might take a bit longer :)
johannes
Powered by blists - more mailing lists