From: Juanlu Herrero <juanlu@fastmail.com>
To: David Wei <dw@davidwei.uk>, netdev@vger.kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
Pavel Begunkov <asml.silence@gmail.com>,
Juanlu Herrero <juanlu@fastmail.com>
Subject: [PATCH net-next v4 0/6] selftests: net: multithreaded multiqueue iou-zcrx
Date: Wed, 29 Jul 2026 17:18:19 -0500 [thread overview]
Message-ID: <20260729221825.42773-1-juanlu@fastmail.com> (raw)
Extend the iou-zcrx selftest to exercise multi-queue zero-copy receive. The
server can now run as N worker threads (-t <n>), each owning a receive queue,
io_uring and zcrx ifq, with each connection dispatched to the worker owning the
queue it landed on. A new rss_multiqueue variant drives traffic across a
multi-queue RSS context; the earlier patches are prep fixes and a refactor.
Changes since v3:
- size the io_uring CQ to the zcrx area buffer count; the default could
overflow and abort a recv with -ENOSPC under multishot load
- Makefile conditional/list cleanup (Jakub)
- drop the anonymous scope blocks in run_server() (Jakub)
- docstrings for the new Python helpers (Jakub)
v3: https://lore.kernel.org/netdev/20260722203950.58550-1-juanlu@fastmail.com/
v2: https://lore.kernel.org/netdev/cover.1776444379.git.juanlu@fastmail.com/
v1: https://lore.kernel.org/netdev/20260408163816.2760-1-juanlu@fastmail.com/
Juanlu Herrero (6):
selftests: net: fix get_refill_ring_size() to use its local variable
selftests: net: remove unused variable in process_recvzc()
selftests: net: refactor server state into struct thread_ctx
selftests: net: add multithread client support to iou-zcrx
selftests: net: add multithread server support to iou-zcrx
selftests: net: add rss_multiqueue test variant to iou-zcrx
.../testing/selftests/drivers/net/hw/Makefile | 7 +-
.../selftests/drivers/net/hw/iou-zcrx.c | 437 +++++++++++++-----
.../selftests/drivers/net/hw/iou-zcrx.py | 50 +-
3 files changed, 366 insertions(+), 128 deletions(-)
base-commit: 2bb54b49e9d522f54dc9c0fe10ba40fbc56041c8
--
2.53.0-Meta
next reply other threads:[~2026-07-29 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 22:18 Juanlu Herrero [this message]
2026-07-29 22:18 ` [PATCH net-next v4 1/6] selftests: net: fix get_refill_ring_size() to use its local variable Juanlu Herrero
2026-07-29 22:18 ` [PATCH net-next v4 2/6] selftests: net: remove unused variable in process_recvzc() Juanlu Herrero
2026-07-29 22:18 ` [PATCH net-next v4 3/6] selftests: net: refactor server state into struct thread_ctx Juanlu Herrero
2026-07-29 22:18 ` [PATCH net-next v4 4/6] selftests: net: add multithread client support to iou-zcrx Juanlu Herrero
2026-07-29 22:18 ` [PATCH net-next v4 5/6] selftests: net: add multithread server " Juanlu Herrero
2026-07-29 22:18 ` [PATCH net-next v4 6/6] selftests: net: add rss_multiqueue test variant " Juanlu Herrero
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=20260729221825.42773-1-juanlu@fastmail.com \
--to=juanlu@fastmail.com \
--cc=asml.silence@gmail.com \
--cc=dw@davidwei.uk \
--cc=kuba@kernel.org \
--cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox