[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c09204f5-4e00-7375-2a22-e09c61b5db49@gmail.com>
Date: Fri, 5 Feb 2021 10:49:59 +0000
From: Edward Cree <ecree.xilinx@...il.com>
To: Eric Dumazet <eric.dumazet@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>
Cc: netdev <netdev@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>,
John Sperbeck <jsperbeck@...gle.com>,
Jian Yang <jianyang@...gle.com>,
Maxim Mikityanskiy <maximmi@...lanox.com>,
Alexander Lobakin <alobakin@...nk.ru>,
Saeed Mahameed <saeedm@...lanox.com>,
Edward Cree <ecree@...arflare.com>
Subject: Re: [PATCH net] net: gro: do not keep too many GRO packets in
napi->rx_list
On 04/02/2021 21:31, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@...gle.com>
>
> Commit c80794323e82 ("net: Fix packet reordering caused by GRO and
> listified RX cooperation") had the unfortunate effect of adding
> latencies in common workloads.
>
> Before the patch, GRO packets were immediately passed to
> upper stacks.
>
> After the patch, we can accumulate quite a lot of GRO
> packets (depdending on NAPI budget).
>
> My fix is counting in napi->rx_count number of segments
> instead of number of logical packets.
>
> Fixes: c80794323e82 ("net: Fix packet reordering caused by GRO and listified RX cooperation")
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
> Bisected-by: John Sperbeck <jsperbeck@...gle.com>
> Tested-by: Jian Yang <jianyang@...gle.com>
> Cc: Maxim Mikityanskiy <maximmi@...lanox.com>
> Cc: Alexander Lobakin <alobakin@...nk.ru>
> Cc: Saeed Mahameed <saeedm@...lanox.com>
> Cc: Edward Cree <ecree@...arflare.com>
Reviewed-by: Edward Cree <ecree.xilinx@...il.com>
Powered by blists - more mailing lists