From: "Alice Mikityanska" <alice.kernel@fastmail.im>
To: "Haishuang Yan" <yanhaishuang@cmss.chinamobile.com>,
netdev@vger.kernel.org
Cc: "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>,
"Daniel Borkmann" <daniel@iogearbox.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] bareudp: Enable BIG TCP packets
Date: Fri, 02 Oct 2026 12:00:45 +0300 [thread overview]
Message-ID: <12e098d5-18b1-4b01-bd55-ccebf8a78bbc@app.fastmail.com> (raw)
In-Reply-To: <20261001042336.224343-1-yanhaishuang@cmss.chinamobile.com>
On Thu, Oct 1, 2026, at 07:23, Haishuang Yan wrote:
> Commit f3d0f753f066 ("vxlan: Enable BIG TCP packets") and commit
> 03ebe91b0f61 ("geneve: Enable BIG TCP packets") allowed BIG TCP on vxlan
> and geneve, after the preceding patches of that series made the common
> UDP tunnel transmit path handle GSO packets larger than 64KB.
>
> bareudp transmits through the same helpers, udp_tunnel_handle_offloads()
> followed by udp_tunnel_xmit_skb() or udp_tunnel6_xmit_skb(), and does
> not fill in any length field itself. Bump tso_max_size up to
> GSO_MAX_SIZE so that the admin can use BIG TCP with bareudp too.
>
> The default gso_max_size and gso_ipv4_max_size stay at 64KB, so nothing
> changes unless they are raised explicitly.
>
> iperf3 TCP over bareudp (ethertype ipv4, IPv4 outer) between two netns
> connected by veth, MTU 1600 on veth, 3 runs of 20 seconds each. This
> was measured in a QEMU TCG guest, so only the relative numbers are
> meaningful:
>
> gso_max_size/gso_ipv4_max_size 65536:
> 4380.6, 4404.2, 4354.5 Mbit/s, average 4379.8 Mbit/s
>
> gso_max_size/gso_ipv4_max_size 196608:
> 5509.4, 5454.7, 5497.4 Mbit/s, average 5487.2 Mbit/s (+25%)
>
> With 196608, about 90k to 100k packets larger than 64KB were
> transmitted on the bareudp device per run, none with 65536. Without
> this patch, setting gso_max_size to 196608 is rejected.
>
> Assisted-by: LLM
> Signed-off-by: Haishuang Yan <yanhaishuang@cmss.chinamobile.com>
> ---
> drivers/net/bareudp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/bareudp.c b/drivers/net/bareudp.c
> index c3b5ed52d877..fcc33e302b9c 100644
> --- a/drivers/net/bareudp.c
> +++ b/drivers/net/bareudp.c
> @@ -589,6 +589,7 @@ static void bareudp_setup(struct net_device *dev)
> dev->max_mtu = IP_MAX_MTU - BAREUDP_BASE_HLEN;
> dev->type = ARPHRD_NONE;
> netif_keep_dst(dev);
> + netif_set_tso_max_size(dev, GSO_MAX_SIZE);
Acked-by: Alice Mikityanska <alice.kernel@fastmail.im>
Do you mind extending the big_tcp_tunnels.sh selftest to cover bareudp?
Besides, enabling BIG TCP with fou would also be a one-liner, the
basement was added in "udp: Support BIG TCP GSO packets where they
can occur":
https://lore.kernel.org/netdev/20260710134242.216538-4-alice.kernel@fastmail.im
> dev->priv_flags |= IFF_NO_QUEUE;
> dev->lltx = true;
> dev->flags = IFF_POINTOPOINT | IFF_NOARP | IFF_MULTICAST;
> --
> 2.43.0
prev parent reply other threads:[~2026-10-02 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 4:23 Haishuang Yan
2026-10-02 9:00 ` Alice Mikityanska [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=12e098d5-18b1-4b01-bd55-ccebf8a78bbc@app.fastmail.com \
--to=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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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
all inboxes | Powered by JetHome®