From: Alexander H Duyck <alexander.duyck@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Alexander Lobakin <alexandr.lobakin@intel.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next 2/3] net: gro: minor optimization for dev_gro_receive()
Date: Thu, 03 Feb 2022 08:39:57 -0800 [thread overview]
Message-ID: <07cd64ccacb61cb933bb66af83cb238caf956c96.camel@gmail.com> (raw)
In-Reply-To: <2a6db6d6ca415cb35cc7b3e4d9424baf0516d782.1643902526.git.pabeni@redhat.com>
On Thu, 2022-02-03 at 16:48 +0100, Paolo Abeni wrote:
> While inspecting some perf report, I noticed that the compiler
> emits suboptimal code for the napi CB initialization, fetching
> and storing multiple times the memory for flags bitfield.
> This is with gcc 10.3.1, but I observed the same with older compiler
> versions.
>
> We can help the compiler to do a nicer work clearing several
> fields at once using an u32 alias. The generated code is quite
> smaller, with the same number of conditional.
>
> Before:
> objdump -t net/core/gro.o | grep " F .text"
> 0000000000000bb0 l F .text 0000000000000357 dev_gro_receive
>
> After:
> 0000000000000bb0 l F .text 000000000000033c dev_gro_receive
>
> RFC -> v1:
> - use __struct_group to delimt the zeroed area (Alexander)
>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> ---
> include/net/gro.h | 52 +++++++++++++++++++++++++--------------------
> --
> net/core/gro.c | 18 +++++++---------
> 2 files changed, 35 insertions(+), 35 deletions(-)
>
> diff --git a/include/net/gro.h b/include/net/gro.h
> index 8f75802d50fd..fa1bb0f0ad28 100644
> --- a/include/net/gro.h
> +++ b/include/net/gro.h
> @@ -29,46 +29,50 @@ struct napi_gro_cb {
> /* Number of segments aggregated. */
> u16 count;
>
> - /* Start offset for remote checksum offload */
> - u16 gro_remcsum_start;
> + /* Used in ipv6_gro_receive() and foo-over-udp */
> + u16 proto;
>
> /* jiffies when first packet was created/queued */
> unsigned long age;
>
> - /* Used in ipv6_gro_receive() and foo-over-udp */
> - u16 proto;
> + /* portion of the cb set to zero at every gro iteration */
> + __struct_group(/* no tag */, zeroed, /* no attrs */,
Any specific reason for using __struct_group here rather than the
struct_group macro instead?
next prev parent reply other threads:[~2022-02-03 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 15:48 [PATCH net-next 0/3] gro: some minor optimization Paolo Abeni
2022-02-03 15:48 ` [PATCH net-next 1/3] net: gro: avoid re-computing truesize twice on recycle Paolo Abeni
2022-02-03 16:16 ` Alexander Lobakin
2022-02-03 15:48 ` [PATCH net-next 2/3] net: gro: minor optimization for dev_gro_receive() Paolo Abeni
2022-02-03 16:09 ` Alexander Lobakin
2022-02-03 16:39 ` Alexander H Duyck [this message]
2022-02-03 17:44 ` Paolo Abeni
2022-02-03 15:48 ` [PATCH net-next 3/3] net: gro: register gso and gro offload on separate lists Paolo Abeni
2022-02-03 16:11 ` Eric Dumazet
2022-02-03 16:26 ` Alexander Lobakin
2022-02-03 16:41 ` Eric Dumazet
2022-02-03 18:07 ` Paolo Abeni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07cd64ccacb61cb933bb66af83cb238caf956c96.camel@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=alexandr.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).