Re: [PATCH v2 net-next 0/4] net: batched receive in GRO path

2018-09-11 Thread Edward Cree
On 07/09/18 03:32, Eric Dumazet wrote: > Adding this complexity and icache pressure needs more experimental results. > What about RPC workloads (eg 100 concurrent netperf -t TCP_RR -- -r > 8000,8000 ) > > Thanks. Some more results.  Note that the TCP_STREAM figures given in the cover  letter were

Re: [PATCH v2 net-next 0/4] net: batched receive in GRO path

2018-09-07 Thread Edward Cree
On 07/09/18 03:32, Eric Dumazet wrote: > Your performance numbers are not convincing, since TCP stream test should > get nominal GRO gains. I'm not quite sure what you mean here, could you explain a bit more? > Adding this complexity and icache pressure needs more experimental results. > > What ab

Re: [PATCH v2 net-next 0/4] net: batched receive in GRO path

2018-09-06 Thread Eric Dumazet
On 09/06/2018 07:24 AM, Edward Cree wrote: > 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. > I have not listified dev_gro_re

[PATCH v2 net-next 0/4] net: batched receive in GRO path

2018-09-06 Thread Edward Cree
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. I have not listified dev_gro_receive() itself, or the per-protocol GRO callback, sin