From: Richard Gobert <richardbgobert@gmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
steffen.klassert@secunet.com, lixiaoyan@google.com,
alexanderduyck@fb.com, leon@kernel.org, ye.xingchen@zte.com.cn,
iwienand@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] gro: optimise redundant parsing of packets
Date: Mon, 30 Jan 2023 14:07:55 +0100 [thread overview]
Message-ID: <20230130130752.GA8015@debian> (raw)
In-Reply-To: <20230130130047.GA7913@debian>
Currently, the IPv6 extension headers are parsed twice: first in
ipv6_gro_receive, and then again in ipv6_gro_complete.
The field NAPI_GRO_CB(skb)->proto is used by GRO to hold the layer 4
protocol type that comes after the IPv6 layer. I noticed that it is set
in ipv6_gro_receive, but isn't used anywhere. By using this field, and
also storing the size of the network header, we can avoid parsing
extension headers a second time in ipv6_gro_complete.
The implementation had to handle both inner and outer layers in case of
encapsulation (as they can't use the same field).
I've applied this optimisation to all base protocols (IPv6, IPv4,
Ethernet). Then, I benchmarked this patch on my machine, using ftrace to
measure ipv6_gro_complete's performance, and there was an improvement.
Signed-off-by: Richard Gobert <richardbgobert@gmail.com>
---
include/net/gro.h | 8 ++++++--
net/ethernet/eth.c | 11 +++++++++--
net/ipv4/af_inet.c | 8 +++++++-
net/ipv6/ip6_offload.c | 15 ++++++++++++---
4 files changed, 34 insertions(+), 8 deletions(-)
diff --git a/include/net/gro.h b/include/net/gro.h
index 7b47dd6ce94f..d364616cb930 100644
--- a/include/net/gro.h
+++ b/include/net/gro.h
@@ -41,8 +41,8 @@ struct napi_gro_cb {
/* Number of segments aggregated. */
u16 count;
- /* Used in ipv6_gro_receive() and foo-over-udp */
- u16 proto;
+ /* Used in eth_gro_receive() */
+ __be16 network_proto;
/* Used in napi_gro_cb::free */
#define NAPI_GRO_FREE 1
@@ -86,6 +86,10 @@ struct napi_gro_cb {
/* used to support CHECKSUM_COMPLETE for tunneling protocols */
__wsum csum;
+
+ /* Used in inet and ipv6 _gro_receive() */
+ u16 network_len;
+ u8 transport_proto;
};
#define NAPI_GRO_CB(skb) ((struct napi_gro_cb *)(skb)->cb)
diff --git a/net/ethernet/eth.c b/net/ethernet/eth.c
index 2edc8b796a4e..d68ad90f0a9e 100644
--- a/net/ethernet/eth.c
+++ b/net/ethernet/eth.c
@@ -439,6 +439,9 @@ struct sk_buff *eth_gro_receive(struct list_head *head, struct sk_buff *skb)
goto out;
}
+ if (!NAPI_GRO_CB(skb)->encap_mark)
+ NAPI_GRO_CB(skb)->network_proto = type;
+
skb_gro_pull(skb, sizeof(*eh));
skb_gro_postpull_rcsum(skb, eh, sizeof(*eh));
@@ -456,12 +459,16 @@ EXPORT_SYMBOL(eth_gro_receive);
int eth_gro_complete(struct sk_buff *skb, int nhoff)
{
struct ethhdr *eh = (struct ethhdr *)(skb->data + nhoff);
- __be16 type = eh->h_proto;
+ __be16 type;
struct packet_offload *ptype;
int err = -ENOSYS;
- if (skb->encapsulation)
+ if (skb->encapsulation) {
skb_set_inner_mac_header(skb, nhoff);
+ type = eh->h_proto;
+ } else {
+ type = NAPI_GRO_CB(skb)->network_proto;
+ }
ptype = gro_find_complete_by_type(type);
if (ptype != NULL)
diff --git a/net/ipv4/af_inet.c b/net/ipv4/af_inet.c
index 6c0ec2789943..4401af7b3a15 100644
--- a/net/ipv4/af_inet.c
+++ b/net/ipv4/af_inet.c
@@ -1551,6 +1551,9 @@ struct sk_buff *inet_gro_receive(struct list_head *head, struct sk_buff *skb)
* immediately following this IP hdr.
*/
+ if (!NAPI_GRO_CB(skb)->encap_mark)
+ NAPI_GRO_CB(skb)->transport_proto = proto;
+
/* Note : No need to call skb_gro_postpull_rcsum() here,
* as we already checked checksum over ipv4 header was 0
*/
@@ -1621,12 +1624,15 @@ int inet_gro_complete(struct sk_buff *skb, int nhoff)
__be16 newlen = htons(skb->len - nhoff);
struct iphdr *iph = (struct iphdr *)(skb->data + nhoff);
const struct net_offload *ops;
- int proto = iph->protocol;
+ int proto;
int err = -ENOSYS;
if (skb->encapsulation) {
skb_set_inner_protocol(skb, cpu_to_be16(ETH_P_IP));
skb_set_inner_network_header(skb, nhoff);
+ proto = iph->protocol;
+ } else {
+ proto = NAPI_GRO_CB(skb)->transport_proto;
}
csum_replace2(&iph->check, iph->tot_len, newlen);
diff --git a/net/ipv6/ip6_offload.c b/net/ipv6/ip6_offload.c
index 00dc2e3b0184..79ba5882f576 100644
--- a/net/ipv6/ip6_offload.c
+++ b/net/ipv6/ip6_offload.c
@@ -227,11 +227,14 @@ INDIRECT_CALLABLE_SCOPE struct sk_buff *ipv6_gro_receive(struct list_head *head,
iph = ipv6_hdr(skb);
}
- NAPI_GRO_CB(skb)->proto = proto;
-
flush--;
nlen = skb_network_header_len(skb);
+ if (!NAPI_GRO_CB(skb)->encap_mark) {
+ NAPI_GRO_CB(skb)->transport_proto = proto;
+ NAPI_GRO_CB(skb)->network_len = nlen;
+ }
+
list_for_each_entry(p, head, list) {
const struct ipv6hdr *iph2;
__be32 first_word; /* <Version:4><Traffic_Class:8><Flow_Label:20> */
@@ -358,7 +361,13 @@ INDIRECT_CALLABLE_SCOPE int ipv6_gro_complete(struct sk_buff *skb, int nhoff)
iph->payload_len = htons(payload_len);
}
- nhoff += sizeof(*iph) + ipv6_exthdrs_len(iph, &ops);
+ if (!skb->encapsulation) {
+ ops = rcu_dereference(inet6_offloads[NAPI_GRO_CB(skb)->transport_proto]);
+ nhoff += NAPI_GRO_CB(skb)->network_len;
+ } else {
+ nhoff += sizeof(*iph) + ipv6_exthdrs_len(iph, &ops);
+ }
+
if (WARN_ON(!ops || !ops->callbacks.gro_complete))
goto out;
--
2.36.1
next prev parent reply other threads:[~2023-01-30 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 13:00 [PATCH 0/2] gro: optimise redundant parsing of packets Richard Gobert
2023-01-30 13:05 ` [PATCH 1/2] gro: decrease size of CB Richard Gobert
2023-01-30 13:07 ` Richard Gobert [this message]
2023-01-30 15:40 ` [PATCH 2/2] gro: optimise redundant parsing of packets Alexander Lobakin
2023-02-22 14:47 ` Richard Gobert
2023-01-30 17:39 ` Eric Dumazet
2023-02-22 14:35 ` 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=20230130130752.GA8015@debian \
--to=richardbgobert@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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=ye.xingchen@zte.com.cn \
--cc=yoshfuji@linux-ipv6.org \
/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).