From: Thomas Bogendoerfer <tbogendoerfer@suse.de>
To: Eric Dumazet <edumazet@google.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net] gro_cells: Avoid packet re-ordering for cloned skbs
Date: Thu, 30 Jan 2025 14:26:31 +0100 [thread overview]
Message-ID: <20250130142631.55651270@samweis> (raw)
In-Reply-To: <CANn89iKSrG40FKLpE3-qbftdXs9Goo61JfkmfXX_1=R5XV-=eQ@mail.gmail.com>
On Wed, 29 Jan 2025 13:06:49 +0100
Eric Dumazet <edumazet@google.com> wrote:
> "TCP Sender in namespace A -> ip6_tunnel -> ipvlan -> ipvlan ->
> ip6_tunnel -> TCP receiver"
> or
> " TCP Sender -> ip6_tunnel -> ipvlan -> ipvlan -> ip6_tunnel -> TCP Receiver"
>
> In this case, GRO in ip6_tunnel is not needed at all, since proper TSO
> packets should already be cooked by TCP sender and be carried
> to the receiver as plain GRO packets.
>
> gro_cells was added at a time GRO layer was only supporting native
> encapsulations : IPv4 + TCP or IPv6 + TCP.
>
> Nowadays, GRO supports encapsulated traffic just fine, same for TSO
> packets encapsulated in ip6_tunnel
>
> Maybe it is time to remove gro_cells from net/ipv6/ip6_tunnel.c
>
> diff --git a/net/ipv6/ip6_tunnel.c b/net/ipv6/ip6_tunnel.c
> index 48fd53b9897265338086136e96ea8e8c6ec3cac..b91c253dc4f1998f8df74251a93e29d00c03db5
> 100644
> --- a/net/ipv6/ip6_tunnel.c
> +++ b/net/ipv6/ip6_tunnel.c
> [...]
this patch works for my test case. So the same thing should be probably
done for net/ipv4/ip_tunnel.c and net/ipv6/ip6_gre.c, too ?
Thomas.
--
SUSE Software Solutions Germany GmbH
HRB 36809 (AG Nürnberg)
Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich
prev parent reply other threads:[~2025-01-30 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 11:50 [PATCH v2 net] gro_cells: Avoid packet re-ordering for cloned skbs Thomas Bogendoerfer
2025-01-21 16:33 ` Eric Dumazet
2025-01-23 8:42 ` Paolo Abeni
2025-01-23 10:07 ` Eric Dumazet
2025-01-23 10:42 ` Paolo Abeni
2025-01-23 10:43 ` Eric Dumazet
2025-01-29 11:31 ` Thomas Bogendoerfer
2025-01-29 11:57 ` Thomas Bogendoerfer
2025-01-29 12:06 ` Eric Dumazet
2025-01-30 13:26 ` Thomas Bogendoerfer [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=20250130142631.55651270@samweis \
--to=tbogendoerfer@suse.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.