mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: Felix Fietkau <nbd@nbd.name>,
	netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: willemdebruijn.kernel@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 net-next v5 6/6] net: add heuristic for enabling TCP fraglist GRO
Date: Thu, 2 May 2024 09:33:05 -0600	[thread overview]
Message-ID: <d35c96ca-3c28-4745-a323-949365f5033a@kernel.org> (raw)
In-Reply-To: <20240502084450.44009-7-nbd@nbd.name>

On 5/2/24 2:44 AM, Felix Fietkau 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
> 
> Acked-by: Paolo Abeni <pabeni@redhat.com>
> Reviewed-by: Eric Dumazet <edumazet@google.com>
> Signed-off-by: Felix Fietkau <nbd@nbd.name>
> ---
>  net/ipv4/tcp_offload.c   | 32 ++++++++++++++++++++++++++++++++
>  net/ipv6/tcpv6_offload.c | 35 +++++++++++++++++++++++++++++++++++
>  2 files changed, 67 insertions(+)
> 

Reviewed-by: David Ahern <dsahern@kernel.org>



      reply	other threads:[~2024-05-02 15:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240502084450.44009-1-nbd@nbd.name>
2024-05-02  8:44 ` [PATCH v5 net-next v5 1/6] net: move skb_gro_receive_list from udp to core Felix Fietkau
2024-05-02 15:32   ` David Ahern
2024-05-02  8:44 ` [PATCH v5 net-next v5 2/6] net: add support for segmenting TCP fraglist GSO packets Felix Fietkau
2024-05-02 15:32   ` David Ahern
2024-05-02  8:44 ` [PATCH v5 net-next v5 3/6] net: add code for TCP fraglist GRO Felix Fietkau
2024-05-02 10:58   ` Eric Dumazet
2024-05-02 15:32   ` David Ahern
2024-05-02  8:44 ` [PATCH v5 net-next v5 4/6] net: create tcp_gro_lookup helper function Felix Fietkau
2024-05-02 15:32   ` David Ahern
2024-05-02  8:44 ` [PATCH v5 net-next v5 5/6] net: create tcp_gro_header_pull " Felix Fietkau
2024-05-02 15:33   ` David Ahern
2024-05-02  8:44 ` [PATCH v5 net-next v5 6/6] net: add heuristic for enabling TCP fraglist GRO Felix Fietkau
2024-05-02 15:33   ` David Ahern [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=d35c96ca-3c28-4745-a323-949365f5033a@kernel.org \
    --to=dsahern@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbd@nbd.name \
    --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

all inboxes | Powered by JetHome®