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, i.maximets@ovn.org, aconole@redhat.com,
echaudro@redhat.com, dev@openvswitch.org
Subject: Re: [PATCH net-next v2] openvswitch: raise internal port TSO limit
Date: Thu, 17 Sep 2026 12:20:04 +0000 [thread overview]
Message-ID: <178964760440.3610434.14071440897470610889.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260916065844.1380155-1-wang.zhan@smartx.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 16 Sep 2026 14:58:44 +0800 you wrote:
> Set the internal port TSO limit to GSO_MAX_SIZE (512 KB), as for
> loopback and veth. This allows the admin/user to set a GSO limit up to
> this value, to use BIG TCP for traffic routed through the internal port.
>
> Only the capability limit changes: the IPv4 and IPv6 GSO and GRO limits
> remain at 64 KiB until changed by the administrator.
>
> [...]
Here is the summary with links:
- [net-next,v2] openvswitch: raise internal port TSO limit
https://git.kernel.org/netdev/net-next/c/859e40055c19
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-17 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 6:58 [PATCH net-next v2] openvswitch: raise internal port TSO limit Wang Zhan
2026-09-16 9:37 ` Eelco Chaudron
2026-09-16 9:49 ` Ilya Maximets
2026-09-16 11:12 ` Eelco Chaudron
2026-09-17 12:20 ` 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=178964760440.3610434.14071440897470610889.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=keyong.sun@smartx.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wang.zhan@smartx.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