From: Xu Xu <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, Xu Du <xudu@redhat.com>
Subject: [RFC net-next 0/8] selftest: Extend tun/virtio coverage for GSO over UDP tunnel
Date: Tue, 2 Dec 2025 13:53:03 +0800 [thread overview]
Message-ID: <cover.1764640939.git.xudu@redhat.com> (raw)
From: Xu Du <xudu@redhat.com>
The primary goal is to add test validation for GSO when operating over
UDP tunnels, a scenario which is not currently covered.
The design strategy is to extend the existing tun/tap testing infrastructure
to support this new use-case, rather than introducing a new or parallel framework.
This allows for better integration and re-use of existing test logic.
---
Link: https://lore.kernel.org/netdev/cover.1763345426.git.xudu@redhat.com/
v1 -> RFC:
- Addresse sporadic failures due to too early send.
- Refactor environment address assign helper function.
Xu Du (8):
selftest: tun: Format tun.c existing code
selftest: tun: Introduce tuntap_helpers.h header for TUN/TAP testing
selftest: tun: Refactor tun_delete to use tuntap_helpers
selftest: tap: Refactor tap test to use tuntap_helpers
selftest: tun: Add helpers for GSO over UDP tunnel
selftest: tun: Add test for sending gso packet into tun
selftest: tun: Add test for receiving gso packet from tun
selftest: tun: Add test data for success and failure paths
tools/testing/selftests/net/tap.c | 286 +-----
tools/testing/selftests/net/tun.c | 915 ++++++++++++++++++-
tools/testing/selftests/net/tuntap_helpers.h | 608 ++++++++++++
3 files changed, 1527 insertions(+), 282 deletions(-)
create mode 100644 tools/testing/selftests/net/tuntap_helpers.h
base-commit: 651765e8d527427e1d91fb7f606c5506f437f622
--
2.49.0
next reply other threads:[~2025-12-02 5:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 5:53 Xu Xu [this message]
2025-12-02 5:53 ` [RFC net-next 1/8] selftest: tun: Format tun.c existing code Xu Xu
2025-12-02 5:53 ` [RFC net-next 2/8] selftest: tun: Introduce tuntap_helpers.h header for TUN/TAP testing Xu Xu
2025-12-02 5:53 ` [RFC net-next 3/8] selftest: tun: Refactor tun_delete to use tuntap_helpers Xu Xu
2025-12-02 5:53 ` [RFC net-next 4/8] selftest: tap: Refactor tap test " Xu Xu
2025-12-02 5:53 ` [RFC net-next 5/8] selftest: tun: Add helpers for GSO over UDP tunnel Xu Xu
2025-12-02 5:53 ` [RFC net-next 6/8] selftest: tun: Add test for sending gso packet into tun Xu Xu
2025-12-02 5:53 ` [RFC net-next 7/8] selftest: tun: Add test for receiving gso packet from tun Xu Xu
2025-12-02 5:53 ` [RFC net-next 8/8] selftest: tun: Add test data for success and failure paths Xu Xu
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.1764640939.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=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.