On 8/12/19 7:51 PM, Ioana Ciocoi Radulescu wrote:
>> -Original Message-
>> From: Edward Cree
>> Sent: Friday, August 9, 2019 8:32 PM
>> To: Ioana Ciocoi Radulescu
>> Cc: David Miller ; netdev ;
>> Eric Dumazet ; linux-net-driv...@solarflare.com
&g
> -Original Message-
> From: Edward Cree
> Sent: Friday, August 9, 2019 8:32 PM
> To: Ioana Ciocoi Radulescu
> Cc: David Miller ; netdev ;
> Eric Dumazet ; linux-net-driv...@solarflare.com
> Subject: Re: [PATCH v3 net-next 0/3] net: batched receive in GRO path
>
On 09/08/2019 18:14, Ioana Ciocoi Radulescu wrote:
> Hi Edward,
>
> I'm probably missing a lot of context here, but is there a reason
> this change targets only the napi_gro_frags() path and not the
> napi_gro_receive() one?
> I'm trying to understand what drivers that don't call napi_gro_frags()
>
> -Original Message-
> From: netdev-ow...@vger.kernel.org On
> Behalf Of Edward Cree
> Sent: Tuesday, August 6, 2019 4:52 PM
> To: David Miller
> Cc: netdev ; Eric Dumazet
> ; linux-net-driv...@solarflare.com
> Subject: [PATCH v3 net-next 0/3] net: batched recei
From: Edward Cree
Date: Tue, 6 Aug 2019 14:52:06 +0100
> This series listifies part of GRO processing, in a manner which allows those
> packets which are not GROed (i.e. for which dev_gro_receive returns
> GRO_NORMAL) to be passed on to the listified regular receive path.
> dev_gro_receive() it
This series listifies part of GRO processing, in a manner which allows those
packets which are not GROed (i.e. for which dev_gro_receive returns
GRO_NORMAL) to be passed on to the listified regular receive path.
dev_gro_receive() itself is not listified, nor the per-protocol GRO
callback, since
