From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Richard Gobert <richardbgobert@gmail.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, alexanderduyck@fb.com,
lixiaoyan@google.com, steffen.klassert@secunet.com,
lucien.xin@gmail.com, ye.xingchen@zte.com.cn,
iwienand@redhat.com, leon@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: RE: [PATCH v2 2/2] gro: optimise redundant parsing of packets
Date: Wed, 22 Feb 2023 10:27:54 -0500 [thread overview]
Message-ID: <63f6347a48c26_3a2320814@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20230222151236.GB12658@debian>
Richard Gobert wrote:
> Currently the IPv6 extension headers are parsed twice: first in
> ipv6_gro_receive, and then again in ipv6_gro_complete.
>
> By using the new ->transport_proto field, and also storing the size of the
> network header, we can avoid parsing extension headers a second time in
> ipv6_gro_complete (which saves multiple memory dereferences and conditional
> checks inside ipv6_exthdrs_len for a varying amount of extension headers in IPv6
> packets).
>
> The implementation had to handle both inner and outer layers in case of
> encapsulation (as they can't use the same field).
>
> Performance tests for TCP stream over IPv6 with a varying amount of extension
> headers demonstrate throughput improvement of ~0.7%.
>
> In addition, I fixed a potential existing problem:
> - The call to skb_set_inner_network_header at the beginning of
> ipv6_gro_complete calculates inner_network_header based on skb->data by
> calling skb_set_inner_network_header, and setting it to point to the beginning
> of the ip header.
> - If a packet is going to be handled by BIG TCP, the following code block is
> going to shift the packet header, and skb->data is going to be changed as
> well.
>
> When the two flows are combined, inner_network_header will point to the wrong
> place.
>
> The fix is to place the whole encapsulation branch after the BIG TCP code block.
This should be a separate fix patch?
> This way, inner_network_header is calculated with a correct value of skb->data.
> Also, by arranging the code that way, the optimisation does not add an additional
> branch.
>
> Signed-off-by: Richard Gobert <richardbgobert@gmail.com>
> ---
> include/net/gro.h | 9 +++++++++
> net/ethernet/eth.c | 14 +++++++++++---
> net/ipv6/ip6_offload.c | 20 +++++++++++++++-----
> 3 files changed, 35 insertions(+), 8 deletions(-)
>
> diff --git a/include/net/gro.h b/include/net/gro.h
> index 7b47dd6ce94f..35f60ea99f6c 100644
> --- a/include/net/gro.h
> +++ b/include/net/gro.h
> @@ -86,6 +86,15 @@ struct napi_gro_cb {
>
> /* used to support CHECKSUM_COMPLETE for tunneling protocols */
> __wsum csum;
> +
> + /* Used in ipv6_gro_receive() */
> + u16 network_len;
> +
> + /* Used in eth_gro_receive() */
> + __be16 network_proto;
> +
Why also cache eth->h_proto? That is not mentioned in the commit message.
> + /* Used in ipv6_gro_receive() */
> + u8 transport_proto;
next prev parent reply other threads:[~2023-02-22 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 14:59 [PATCH v2 0/2] gro: optimise redundant parsing of packets Richard Gobert
2023-02-22 15:07 ` [PATCH v2 1/2] gro: decrease size of CB Richard Gobert
2023-02-22 15:12 ` [PATCH v2 2/2] gro: optimise redundant parsing of packets Richard Gobert
2023-02-22 15:27 ` Willem de Bruijn [this message]
2023-02-22 15:41 ` Eric Dumazet
2023-02-23 19:12 ` Richard Gobert
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=63f6347a48c26_3a2320814@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=alexanderduyck@fb.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=iwienand@redhat.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardbgobert@gmail.com \
--cc=steffen.klassert@secunet.com \
--cc=ye.xingchen@zte.com.cn \
/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).