[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1735314f-3c6a-45fc-0270-b90cc4d5d6ba@gmail.com>
Date: Wed, 10 Jul 2019 17:41:29 +0200
From: Eric Dumazet <eric.dumazet@...il.com>
To: Edward Cree <ecree@...arflare.com>,
Paolo Abeni <pabeni@...hat.com>,
David Miller <davem@...emloft.net>
Cc: netdev <netdev@...r.kernel.org>,
Eric Dumazet <eric.dumazet@...il.com>
Subject: Re: [RFC PATCH net-next 0/3] net: batched receive in GRO path
On 7/10/19 4:52 PM, Edward Cree wrote:
> Hmm, I was caught out by the call to napi_poll() actually being a local
> function pointer, not the static function of the same name. How did a
> shadow like that ever get allowed?
> But in that case I _really_ don't understand napi_busy_loop(); nothing
> in it seems to ever flush GRO, so it's relying on either
> (1) stuff getting flushed because the bucket runs out of space, or
> (2) the next napi poll after busy_poll_stop() doing the flush.
> What am I missing, and where exactly in napi_busy_loop() should the
> gro_normal_list() call go?
Please look at busy_poll_stop()
Powered by blists - more mailing lists