From: Xu Du <xudu@redhat.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [RFC net-next 0/4] selftests: drv-net: tso: add double tunneling GSO tests
Date: Tue, 7 Apr 2026 10:45:07 +0800 [thread overview]
Message-ID: <cover.1775527362.git.xudu@redhat.com> (raw)
This series extends the TSO selftest (tso.py) to cover double-encapsulated
tunnel scenarios, ensuring that hardware offload and the kernel GSO path
correctly handle packets with two layers of tunnel headers.
Xu Du (4):
selftests: drv-net: tso: retry connect on EHOSTUNREACH
selftests: drv-net: tso: add helpers for double tunneling GSO
selftests: drv-net: tso: add Geneve double tunneling GSO test
selftests: drv-net: tso: expand double tunnel GSO test coverage
.../drivers/net/hw/lib/py/__init__.py | 4 +-
tools/testing/selftests/drivers/net/hw/tso.py | 267 +++++++++++++++---
.../selftests/drivers/net/lib/py/__init__.py | 4 +-
.../testing/selftests/net/lib/py/__init__.py | 4 +-
tools/testing/selftests/net/lib/py/utils.py | 19 +-
5 files changed, 248 insertions(+), 50 deletions(-)
base-commit: 2f60df9e61aa48bf40c36254bf2e839f09cffd98
--
2.53.0
next reply other threads:[~2026-04-07 2:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 2:45 Xu Du [this message]
2026-04-07 2:45 ` [RFC net-next 1/4] selftests: drv-net: tso: retry connect on EHOSTUNREACH Xu Du
2026-04-07 2:45 ` [RFC net-next 2/4] selftests: drv-net: tso: add helpers for double tunneling GSO Xu Du
2026-04-07 15:08 ` Jakub Kicinski
2026-04-08 2:04 ` Xu Du
2026-04-09 0:27 ` Jakub Kicinski
2026-04-09 7:35 ` Xu Du
2026-04-10 2:23 ` Jakub Kicinski
2026-04-07 2:45 ` [RFC net-next 3/4] selftests: drv-net: tso: add Geneve double tunneling GSO test Xu Du
2026-04-07 2:45 ` [RFC net-next 4/4] selftests: drv-net: tso: expand double tunnel GSO test coverage Xu Du
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=cover.1775527362.git.xudu@redhat.com \
--to=xudu@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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.