From: patchwork-bot+netdevbpf@kernel.org
To: Haishuang Yan <yanhaishuang@cmss.chinamobile.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
shuah@kernel.org, willemb@google.com, martin.varghese@nokia.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] selftests: net: bareudp: Add stream tests with software GSO
Date: Sat, 17 Oct 2026 01:00:04 +0000 [thread overview]
Message-ID: <179219880453.1036979.10660617907631873516.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261011104300.1606351-1-yanhaishuang@cmss.chinamobile.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 11 Oct 2026 18:43:00 +0800 you wrote:
> The bareudp tests only send pings, which are not GSO packets, so the
> segmentation path of bareudp is not covered.
>
> Copy a file over TCP from NS0 to NS3 with socat after the IPv4 and IPv6
> ping tests, with UDP tunnel segmentation offload disabled on the
> underlay veths, so that the GSO packets encapsulated by bareudp are
> segmented in software. Raise the MTU of the underlay veths, so that full
> sized packets fit with the encapsulation, as there is no path MTU
> discovery through bareudp.
>
> [...]
Here is the summary with links:
- [net-next,v2] selftests: net: bareudp: Add stream tests with software GSO
https://git.kernel.org/netdev/net-next/c/f42d67a5044e
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-10-17 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 10:43 [PATCH net-next v2] selftests: net: bareudp: Add stream tests with software GSO Haishuang Yan
2026-10-16 19:07 ` Simon Horman
2026-10-17 1:00 ` 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=179219880453.1036979.10660617907631873516.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.varghese@nokia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemb@google.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 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.