All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Wang Zhan <wang.zhan@smartx.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	keyong.sun@smartx.com, willemdebruijn.kernel@gmail.com,
	jasowangio@gmail.com, andrew+netdev@lunn.ch, aconole@redhat.com,
	echaudro@redhat.com, i.maximets@ovn.org, dev@openvswitch.org,
	daniel@iogearbox.net, ncardwell@google.com, kuniyu@google.com,
	alice@isovalent.com, david.laight.linux@gmail.com
Subject: Re: [PATCH net-next v5 0/6] net: re-segment oversized TCP GSO skbs
Date: Tue, 13 Oct 2026 13:40:05 +0000	[thread overview]
Message-ID: <179189880587.311420.10716275190356671758.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261008100651.2534957-1-wang.zhan@smartx.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Thu,  8 Oct 2026 18:06:45 +0800 you wrote:
> BIG TCP is negotiated per netdevice, so BIG TCP and non-BIG TCP ports can
> coexist in one path.  When an skb exceeds the GSO limits of the port it is
> sent to, it loses its GSO feature mask and is segmented into individual MSS
> sized packets, which that port then sends without TSO.
> 
> This series cuts such a TCP GSO skb into GSO skbs which fit the device
> limits instead, so the rest of the path keeps using TSO.  On a
> veth -> bridge -> TAP -> guest virtio-net path, with BIG TCP enabled on the
> veth endpoints and left off in the guest, a single iperf3 TCP flow, six
> alternating runs per state (-t 15 -O 5, fixed CPU affinity and port tuple):
> 
> [...]

Here is the summary with links:
  - [net-next,v5,1/6] net: core: use the packet's L3 protocol for the GSO size limit
    https://git.kernel.org/netdev/net-next/c/cc9dcb0e7a42
  - [net-next,v5,2/6] net: core: factor out the GSO device limit check
    https://git.kernel.org/netdev/net-next/c/0bba48256b0a
  - [net-next,v5,3/6] net: gso: support re-segmentation of TCP GSO skbs
    https://git.kernel.org/netdev/net-next/c/c4076626ba52
  - [net-next,v5,4/6] net: gso: clear the GSO state of the last output segment
    https://git.kernel.org/netdev/net-next/c/335a0378a755
  - [net-next,v5,5/6] net: core: re-segment oversized TCP GSO skbs
    https://git.kernel.org/netdev/net-next/c/32bfd220cd6f
  - [net-next,v5,6/6] net: net_test: add tests for TCP re-segmentation
    https://git.kernel.org/netdev/net-next/c/a374c5bb41d1

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-13 13:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 10:06 [PATCH net-next v5 0/6] net: re-segment oversized TCP GSO skbs Wang Zhan
2026-10-08 10:06 ` [PATCH net-next v5 1/6] net: core: use the packet's L3 protocol for the GSO size limit Wang Zhan
2026-10-08 10:06 ` [PATCH net-next v5 2/6] net: core: factor out the GSO device limit check Wang Zhan
2026-10-08 10:06 ` [PATCH net-next v5 3/6] net: gso: support re-segmentation of TCP GSO skbs Wang Zhan
2026-10-08 10:06 ` [PATCH net-next v5 4/6] net: gso: clear the GSO state of the last output segment Wang Zhan
2026-10-08 18:37   ` Willem de Bruijn
2026-10-08 10:06 ` [PATCH net-next v5 5/6] net: core: re-segment oversized TCP GSO skbs Wang Zhan
2026-10-08 10:06 ` [PATCH net-next v5 6/6] net: net_test: add tests for TCP re-segmentation Wang Zhan
2026-10-08 18:38   ` Willem de Bruijn
2026-10-13 13:34   ` Paolo Abeni
2026-10-13 13:40 ` patchwork-bot+netdevbpf [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=179189880587.311420.10716275190356671758.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aconole@redhat.com \
    --cc=alice@isovalent.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=david.laight.linux@gmail.com \
    --cc=dev@openvswitch.org \
    --cc=echaudro@redhat.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=i.maximets@ovn.org \
    --cc=jasowangio@gmail.com \
    --cc=keyong.sun@smartx.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wang.zhan@smartx.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 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.