From: Simon Horman <horms@kernel.org>
To: Haishuang Yan <yanhaishuang@cmss.chinamobile.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Alice Mikityanska <alice.kernel@fastmail.im>,
Daniel Borkmann <daniel@iogearbox.net>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 2/2] selftests: net: big_tcp_tunnels: Cover bareudp
Date: Fri, 16 Oct 2026 20:11:30 +0100 [thread overview]
Message-ID: <20261016191130.GQ363352@horms.kernel.org> (raw)
In-Reply-To: <20261011102023.1603595-3-yanhaishuang@cmss.chinamobile.com>
On Sun, Oct 11, 2026 at 06:20:23PM +0800, Haishuang Yan wrote:
> Now that bareudp allows BIG TCP too, run the same checks over bareudp as
> for vxlan and geneve.
>
> bareudp only works in external mode, so attach the tunnel metadata to
> all packets sent through the device with a tc tunnel_key action on
> egress. The device uses ethertype ipv4 with multiproto, so that both
> IPv4 and IPv6 traffic can go through it. Its MTU does not account for
> the encapsulation, so lower it to leave room for the IPv6 and UDP
> headers, otherwise the encapsulated packets would be fragmented.
>
> Assisted-by: LLM
> Signed-off-by: Haishuang Yan <yanhaishuang@cmss.chinamobile.com>
Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2026-10-16 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 10:20 [PATCH net-next v4 0/2] bareudp: Enable BIG TCP packets Haishuang Yan
2026-10-11 10:20 ` [PATCH net-next v4 1/2] " Haishuang Yan
2026-10-16 19:10 ` Simon Horman
2026-10-11 10:20 ` [PATCH net-next v4 2/2] selftests: net: big_tcp_tunnels: Cover bareudp Haishuang Yan
2026-10-16 19:11 ` Simon Horman [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=20261016191130.GQ363352@horms.kernel.org \
--to=horms@kernel.org \
--cc=alice.kernel@fastmail.im \
--cc=andrew+netdev@lunn.ch \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=yanhaishuang@cmss.chinamobile.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