[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3f6cd784-767e-02e3-0c30-c0dda12e51ab@intel.com>
Date: Fri, 2 Jun 2023 16:22:19 +0200
From: Alexander Lobakin <aleksander.lobakin@...el.com>
To: Richard Gobert <richardbgobert@...il.com>
CC: <davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
<pabeni@...hat.com>, <lixiaoyan@...gle.com>,
<lucien.xin@...il.com>, <alexanderduyck@...com>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/1] gro: decrease size of CB
From: Richard Gobert <richardbgobert@...il.com>
Date: Thu, 1 Jun 2023 18:09:28 +0200
> This patch frees up space in the GRO CB, which is currently at its maximum
> size. This patch was submitted and reviewed previously in a patch series,
> but is now reposted as a standalone patch, as suggested by Paolo.
> (https://lore.kernel.org/netdev/889f2dc5e646992033e0d9b0951d5a42f1907e07.camel@redhat.com/)
>
> Changelog:
>
> v2 -> v3:
> * add comment
>
> v1 -> v2:
> * remove inline keyword
I hope you've checked that there's no difference in object code with and
w/o `inline`? Sometimes the compilers do weird things and stop inlining
oneliners if they're used more than once. skb_gro_reset_offset() is
marked `inline` exactly due to that =\
>
> Richard Gobert (1):
> gro: decrease size of CB
>
> include/net/gro.h | 26 ++++++++++++++++----------
> net/core/gro.c | 19 ++++++++++++-------
> 2 files changed, 28 insertions(+), 17 deletions(-)
Thanks,
Olek
Powered by blists - more mailing lists