[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANn89iKmJg641Wz7uJkcbdGd41+Vu4_eT7xtWv_V-rmyQhmyBQ@mail.gmail.com>
Date: Mon, 15 Mar 2021 09:50:40 +0100
From: Eric Dumazet <edumazet@...gle.com>
To: Alexander Lobakin <alobakin@...me>
Cc: "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andriin@...com>, Wei Wang <weiwan@...gle.com>,
Cong Wang <cong.wang@...edance.com>,
Taehee Yoo <ap420073@...il.com>,
netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 net-next 0/3] gro: micro-optimize dev_gro_receive()
On Sat, Mar 13, 2021 at 9:30 PM Alexander Lobakin <alobakin@...me> wrote:
>
> This random series addresses some of suboptimal constructions used
> in the main GRO entry point.
> The main body is gro_list_prepare() simplification and pointer usage
> optimization in dev_gro_receive() itself. Being mostly cosmetic, it
> gives like +10 Mbps on my setup to both TCP and UDP (both single- and
> multi-flow).
>
> Since v1 [0]:
> - drop the replacement of bucket index calculation with
> reciprocal_scale() since it makes absolutely no sense (Eric);
> - improve stack usage in dev_gro_receive() (Eric);
> - reverse the order of patches to avoid changes superseding.
>
> [0] https://lore.kernel.org/netdev/20210312162127.239795-1-alobakin@pm.me
>
SGTM, thanks.
Reviewed-by: Eric Dumazet <edumaet@...gle.com>
Powered by blists - more mailing lists