From: Alexander Lobakin <alexandr.lobakin@intel.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Alexander Lobakin <alexandr.lobakin@intel.com>,
netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: [RFC PATCH 2/3] net: gro: minor optimization for dev_gro_receive()
Date: Tue, 18 Jan 2022 16:56:20 +0100 [thread overview]
Message-ID: <20220118155620.27706-1-alexandr.lobakin@intel.com> (raw)
In-Reply-To: <35d722e246b7c4afb6afb03760df6f664db4ef05.1642519257.git.pabeni@redhat.com>
From: Paolo Abeni <pabeni@redhat.com>
Date: Tue, 18 Jan 2022 16:24:19 +0100
> 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 e.g. initially setting
> all the bitfield to 0 using an u16 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
>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> ---
> include/net/gro.h | 13 +++++++++----
> net/core/gro.c | 16 +++++-----------
> 2 files changed, 14 insertions(+), 15 deletions(-)
>
> diff --git a/include/net/gro.h b/include/net/gro.h
> index 8f75802d50fd..a068b27d341f 100644
> --- a/include/net/gro.h
> +++ b/include/net/gro.h
> @@ -29,14 +29,17 @@ 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 */
> + u32 zeroed_start[0];
> +
> + /* Start offset for remote checksum offload */
> + u16 gro_remcsum_start;
>
> /* This is non-zero if the packet may be of the same flow. */
> u8 same_flow:1;
> @@ -70,6 +73,8 @@ struct napi_gro_cb {
> /* GRO is done by frag_list pointer chaining. */
> u8 is_flist:1;
>
> + u32 zeroed_end[0];
This should be wrapped in struct_group() I believe, or compilers
will start complaining soon. See [0] for the details.
Adding Kees to the CCs.
> +
> /* used to support CHECKSUM_COMPLETE for tunneling protocols */
> __wsum csum;
>
> diff --git a/net/core/gro.c b/net/core/gro.c
> index d43d42215bdb..b9ebe9298731 100644
> --- a/net/core/gro.c
> +++ b/net/core/gro.c
> @@ -435,6 +435,9 @@ static void gro_flush_oldest(struct napi_struct *napi, struct list_head *head)
> napi_gro_complete(napi, oldest);
> }
>
> +#define zeroed_len (offsetof(struct napi_gro_cb, zeroed_end) - \
> + offsetof(struct napi_gro_cb, zeroed_start))
> +
> static enum gro_result dev_gro_receive(struct napi_struct *napi, struct sk_buff *skb)
> {
> u32 bucket = skb_get_hash_raw(skb) & (GRO_HASH_BUCKETS - 1);
> @@ -459,29 +462,20 @@ static enum gro_result dev_gro_receive(struct napi_struct *napi, struct sk_buff
>
> skb_set_network_header(skb, skb_gro_offset(skb));
> skb_reset_mac_len(skb);
> - NAPI_GRO_CB(skb)->same_flow = 0;
> + BUILD_BUG_ON(zeroed_len != sizeof(NAPI_GRO_CB(skb)->zeroed_start[0]));
> + NAPI_GRO_CB(skb)->zeroed_start[0] = 0;
> NAPI_GRO_CB(skb)->flush = skb_is_gso(skb) || skb_has_frag_list(skb);
> - NAPI_GRO_CB(skb)->free = 0;
> - NAPI_GRO_CB(skb)->encap_mark = 0;
> - NAPI_GRO_CB(skb)->recursion_counter = 0;
> - NAPI_GRO_CB(skb)->is_fou = 0;
> NAPI_GRO_CB(skb)->is_atomic = 1;
> - NAPI_GRO_CB(skb)->gro_remcsum_start = 0;
>
> /* Setup for GRO checksum validation */
> switch (skb->ip_summed) {
> case CHECKSUM_COMPLETE:
> NAPI_GRO_CB(skb)->csum = skb->csum;
> NAPI_GRO_CB(skb)->csum_valid = 1;
> - NAPI_GRO_CB(skb)->csum_cnt = 0;
> break;
> case CHECKSUM_UNNECESSARY:
> NAPI_GRO_CB(skb)->csum_cnt = skb->csum_level + 1;
> - NAPI_GRO_CB(skb)->csum_valid = 0;
> break;
> - default:
> - NAPI_GRO_CB(skb)->csum_cnt = 0;
> - NAPI_GRO_CB(skb)->csum_valid = 0;
> }
>
> pp = INDIRECT_CALL_INET(ptype->callbacks.gro_receive,
> --
> 2.34.1
[0] https://lore.kernel.org/linux-hardening/20220112220652.3952944-1-keescook@chromium.org
Thanks,
Al
next prev parent reply other threads:[~2022-01-18 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 15:24 [RFC PATCH 0/3] gro: some minor optimizations Paolo Abeni
2022-01-18 15:24 ` [RFC PATCH 1/3] net: gro: avoid re-computing truesize twice on recycle Paolo Abeni
2022-01-18 15:24 ` [RFC PATCH 2/3] net: gro: minor optimization for dev_gro_receive() Paolo Abeni
2022-01-18 15:56 ` Alexander Lobakin [this message]
2022-01-18 16:31 ` Paolo Abeni
2022-01-18 17:39 ` Alexander Lobakin
2022-02-02 10:09 ` Paolo Abeni
2022-02-02 12:08 ` Alexander Lobakin
2022-02-07 2:53 ` Kees Cook
2022-01-18 15:24 ` [RFC PATCH 3/3] net: gro: register gso and gro offload on separate lists 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=20220118155620.27706-1-alexandr.lobakin@intel.com \
--to=alexandr.lobakin@intel.com \
--cc=edumazet@google.com \
--cc=keescook@chromium.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