From: Daniel Borkmann <daniel@iogearbox.net>
To: kuba@kernel.org
Cc: razor@blackwall.org, bobbyeshleman@meta.com, dw@davidwei.uk,
netdev@vger.kernel.org
Subject: [PATCH net-next 0/4] Extend netkit io_uring ZC selftests
Date: Wed, 10 Jun 2026 10:03:40 +0200 [thread overview]
Message-ID: <20260610080344.701380-1-daniel@iogearbox.net> (raw)
Small follow-up to the HW net selftests, in particular to add a
selftest showing that also large rx_buf_len for io_uring ZC is
supported with netkit queue leasing.
Daniel Borkmann (4):
selftests/net: Move netkit lease hw setup into per-test fixtures
selftests/net: Use public NetDrvContEnv API in nk_qlease fixtures
selftests/net: Add netkit io_uring ZC test for large rx_buf_len
selftests/net: Add hugepage kernel config dependency for zcrx
tools/testing/selftests/drivers/net/hw/config | 1 +
.../selftests/drivers/net/hw/nk_qlease.py | 277 ++++++++++++++----
.../selftests/drivers/net/lib/py/env.py | 36 ++-
3 files changed, 250 insertions(+), 64 deletions(-)
--
2.43.0
next reply other threads:[~2026-06-10 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 8:03 Daniel Borkmann [this message]
2026-06-10 8:03 ` [PATCH net-next 1/4] selftests/net: Move netkit lease hw setup into per-test fixtures Daniel Borkmann
2026-06-10 23:50 ` Bobby Eshleman
2026-06-10 8:03 ` [PATCH net-next 2/4] selftests/net: Use public NetDrvContEnv API in nk_qlease fixtures Daniel Borkmann
2026-06-10 23:53 ` Bobby Eshleman
2026-06-10 8:03 ` [PATCH net-next 3/4] selftests/net: Add netkit io_uring ZC test for large rx_buf_len Daniel Borkmann
2026-06-10 23:28 ` Bobby Eshleman
2026-06-10 8:03 ` [PATCH net-next 4/4] selftests/net: Add hugepage kernel config dependency for zcrx Daniel Borkmann
2026-06-10 23:54 ` Bobby Eshleman
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=20260610080344.701380-1-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=bobbyeshleman@meta.com \
--cc=dw@davidwei.uk \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox