From: Felix Fietkau <nbd@nbd.name>
To: Eric Dumazet <edumazet@google.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
willemdebruijn.kernel@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next v2 5/5] net: add heuristic for enabling TCP fraglist GRO
Date: Thu, 25 Apr 2024 17:29:04 +0200 [thread overview]
Message-ID: <554bd11b-376e-4d68-ad79-01e5202deaf8@nbd.name> (raw)
In-Reply-To: <CANn89iLqpADT6T_JtecgMJKKcTEBORVdVqTYYBRtwWWnk6=4ng@mail.gmail.com>
On 25.04.24 17:26, Eric Dumazet wrote:
> On Thu, Apr 25, 2024 at 5:04 PM Felix Fietkau <nbd@nbd.name> wrote:
>>
>> When forwarding TCP after GRO, software segmentation is very expensive,
>> especially when the checksum needs to be recalculated.
>> One case where that's currently unavoidable is when routing packets over
>> PPPoE. Performance improves significantly when using fraglist GRO
>> implemented in the same way as for UDP.
>>
>> When NETIF_F_GRO_FRAGLIST is enabled, perform a lookup for an established
>> socket in the same netns as the receiving device. While this may not
>> cover all relevant use cases in multi-netns configurations, it should be
>> good enough for most configurations that need this.
>>
>> Here's a measurement of running 2 TCP streams through a MediaTek MT7622
>> device (2-core Cortex-A53), which runs NAT with flow offload enabled from
>> one ethernet port to PPPoE on another ethernet port + cake qdisc set to
>> 1Gbps.
>>
>> rx-gro-list off: 630 Mbit/s, CPU 35% idle
>> rx-gro-list on: 770 Mbit/s, CPU 40% idle
>>
>> Signe-off-by: Felix Fietkau <nbd@nbd.name>
>> ---
>> net/ipv4/tcp_offload.c | 48 +++++++++++++++++++++++++++++++++++++
>> net/ipv6/tcpv6_offload.c | 51 ++++++++++++++++++++++++++++++++++++++++
>> 2 files changed, 99 insertions(+)
>>
>> diff --git a/net/ipv4/tcp_offload.c b/net/ipv4/tcp_offload.c
>> index 520fd425ab19..3bb96a110402 100644
>> --- a/net/ipv4/tcp_offload.c
>> +++ b/net/ipv4/tcp_offload.c
>> @@ -405,6 +405,52 @@ void tcp_gro_complete(struct sk_buff *skb)
>> }
>> EXPORT_SYMBOL(tcp_gro_complete);
>>
>> +static void tcp4_check_fraglist_gro(struct list_head *head, struct sk_buff *skb)
>> +{
>> + const struct iphdr *iph = skb_gro_network_header(skb);
>
> I do not think loading iph before all skb_gro_header() and
> skb_gro_header_slow() calls is wise.
>
> pskb_may_pull() can re-allocate skb->head
Will fix.
>> + struct net *net = dev_net(skb->dev);
>> + unsigned int off, hlen, thlen;
>> + struct sk_buff *p;
>> + struct tcphdr *th;
>> + struct sock *sk;
>> + int iif, sdif;
>> +
>> + if (!(skb->dev->features & NETIF_F_GRO_FRAGLIST))
>> + return;
>> +
>> + off = skb_gro_offset(skb);
>> + hlen = off + sizeof(*th);
>> + th = skb_gro_header(skb, hlen, off);
>> + if (unlikely(!th))
>> + return;
>> +
>> + thlen = th->doff * 4;
>> + if (thlen < sizeof(*th))
>> + return;
>> +
>> + hlen = off + thlen;
>> + if (!skb_gro_may_pull(skb, hlen)) {
>> + th = skb_gro_header_slow(skb, hlen, off);
>> + if (unlikely(!th))
>> + return;
>> + }
>> +
>> + p = tcp_gro_lookup(head, th);
>> + if (p) {
>> + NAPI_GRO_CB(skb)->is_flist = NAPI_GRO_CB(p)->is_flist;
>> + return;
>> + }
>> +
>> + inet_get_iif_sdif(skb, &iif, &sdif);
>> + sk = __inet_lookup_established(net, net->ipv4.tcp_death_row.hashinfo,
>> + iph->saddr, th->source,
>> + iph->daddr, ntohs(th->dest),
>> + iif, sdif);
>> + NAPI_GRO_CB(skb)->is_flist = !sk;
>> + if (sk)
>> + sock_put(sk);
>> +}
>> +
>> INDIRECT_CALLABLE_SCOPE
>> struct sk_buff *tcp4_gro_receive(struct list_head *head, struct sk_buff *skb)
>> {
>> @@ -416,6 +462,8 @@ struct sk_buff *tcp4_gro_receive(struct list_head *head, struct sk_buff *skb)
>> return NULL;
>> }
>>
>
> I would probably pull the whole TCP header here, before calling
> tcp4_check_fraglist_gro(head, skb)
> and no longer do this twice from tcp4_check_fraglist_gro() and tcp_gro_receive()
>
> Perhaps define a new inline helper, that will be called from
> tcp4_gro_receive() and tcp6_gro_receive(),
> and not anymore from tcp_gro_receive()
>
> static inline struct tcphdr *tcp_gro_pull_header(...)
> {
> ....
> off = skb_gro_offset(skb);
> hlen = off + sizeof(*th);
> th = skb_gro_header(skb, hlen, off);
> if (unlikely(!th))
> return NULL;
>
> thlen = th->doff * 4;
> if (thlen < sizeof(*th))
> return NULL;
>
> hlen = off + thlen;
> if (!skb_gro_may_pull(skb, hlen))
> th = skb_gro_header_slow(skb, hlen, off);
>
> return th;
> }
Makes sense
Thanks,
- Felix
prev parent reply other threads:[~2024-04-25 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 15:04 [PATCH v2 net-next 0/5] Add TCP fraglist GRO support Felix Fietkau
2024-04-25 15:04 ` [PATCH v2 net-next v2 1/5] net: move skb_gro_receive_list from udp to core Felix Fietkau
2024-04-25 15:04 ` [PATCH v2 net-next v2 2/5] net: add support for segmenting TCP fraglist GSO packets Felix Fietkau
2024-04-25 15:17 ` Willem de Bruijn
2024-04-25 15:22 ` Felix Fietkau
2024-04-25 15:04 ` [PATCH v2 net-next v2 3/5] net: add code for TCP fraglist GRO Felix Fietkau
2024-04-25 15:18 ` Willem de Bruijn
2024-04-25 15:26 ` Felix Fietkau
2024-04-25 15:04 ` [PATCH v2 net-next v2 4/4] net: add heuristic for enabling " Felix Fietkau
2024-04-25 15:04 ` [PATCH v2 net-next v2 4/5] net: create tcp_gro_lookup helper function Felix Fietkau
2024-04-25 15:04 ` [PATCH v2 net-next v2 5/5] net: add heuristic for enabling TCP fraglist GRO Felix Fietkau
2024-04-25 15:26 ` Eric Dumazet
2024-04-25 15:29 ` Felix Fietkau [this message]
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=554bd11b-376e-4d68-ad79-01e5202deaf8@nbd.name \
--to=nbd@nbd.name \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemdebruijn.kernel@gmail.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