Thread (32 messages) 32 messages, 8 authors, 6d ago

Re: [PATCH net-next v9 0/9] BIG TCP for UDP tunnels

From: Alice Mikityanska <hidden>
Date: 2026-07-23 14:19:57

On Wed, 22 Jul 2026 at 15:01, Paolo Abeni [off-list ref] wrote:
On 7/10/26 3:42 PM, Alice Mikityanska wrote:
quoted
From: Alice Mikityanska <redacted>

This series is a follow-up to "BIG TCP without HBH in IPv6", and it adds
support for BIG TCP IPv4/IPv6 workloads in vxlan and geneve. Now that
IPv6 BIG TCP doesn't require stripping the HBH in all various
combinations in tunneled traffic, adding BIG TCP becomes feasible.

Patch 01 adds accessors for the length field in the UDP header, as
suggested by Paolo in review. The usage of udp_set_len is then added in
the following patches that start using length=0 in BIG TCP UDP packets.

Patches 02-04 close the gaps that prevent BIG TCP packets from going
through UDP tunnel code.

Patch 05 validates packets in udp_gro_receive to exclude packets with
length=0 from GRO aggregation.

Patch 06 is for proper formatting in tcpdump (set UDP len to 0 rather
than a trimmed value on overflow).

Patches 07-08 bump up tso_max_size for VXLAN and GENEVE.

Patch 09 adds selftests.
Thanks for the effort and the persistence! I understand the frustration
with AI review and discontinuous feedback, unfortunately the volume of
patches on the ML makes such sloops more frequent than before.

I merged this version, addressing an hopefully trivial conflict.
Thanks so much! I'm preparing the follow-ups on the gso_segs overflow
first, then I hope to address the other points about compatibility
with GRO hints, early flush of malformed packets, and to explore UDP
GRO > 64k.
@Breno:
a second pair of eyes on the resolution would be appreciated.

@Alice: please follow-up on the possible gso_segs overflow ASAP.

Thanks,

Paolo
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help