From: Juanlu Herrero <juanlu@fastmail.com>
To: netdev@vger.kernel.org, dw@davidwei.uk
Cc: io-uring@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, kuba@kernel.org,
asml.silence@gmail.com, pabeni@redhat.com, shuah@kernel.org,
Juanlu Herrero <juanlu@fastmail.com>
Subject: [PATCH net-next v5 0/6] selftests: net: multithreaded multiqueue iou-zcrx
Date: Thu, 13 Aug 2026 20:23:42 -0500 [thread overview]
Message-ID: <20260814012348.46958-1-juanlu@fastmail.com> (raw)
This series extends the iou-zcrx selftests to be multithreaded while
preserving existing single-threaded tests.
Patches 1 and 2 are prep fixes/cleanups. Patch 3 refactors the server's
global state. Patches 4 and 5 add the multithreaded client and server.
Finally, patch 6 adds the python side multithreaded test case.
Changes since v4:
- In patch 4, make cfg_num_threads the default value and remove
CONNS_PER_THREAD and associated ternary (David)
- Use reverse christmas tree for variables (Paolo, David)
- Address race condition identified by Sashiko (Paolo)
- use thread barriers to get rid of epoll in the main thread (David)
- Make napi id matcher helper take a connfd as a param and return the
index directly (David)
v4: https://lore.kernel.org/netdev/20260729221825.42773-1-juanlu@fastmail.com/
v3: https://lore.kernel.org/netdev/20260722203950.58550-1-juanlu@fastmail.com/
v2: https://lore.kernel.org/netdev/20260418094907.3cde57ca@kernel.org/
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 | 406 ++++++++++++------
.../selftests/drivers/net/hw/iou-zcrx.py | 50 ++-
3 files changed, 332 insertions(+), 131 deletions(-)
base-commit: 3da8c3c8b8fa99505624b65ef590482f48e766b6
--
2.53.0-Meta
next reply other threads:[~2026-08-14 1:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 1:23 Juanlu Herrero [this message]
2026-08-14 1:23 ` [PATCH net-next v5 1/6] selftests: net: fix get_refill_ring_size() to use its local variable Juanlu Herrero
2026-08-14 1:23 ` [PATCH net-next v5 2/6] selftests: net: remove unused variable in process_recvzc() Juanlu Herrero
2026-08-14 1:23 ` [PATCH net-next v5 3/6] selftests: net: refactor server state into struct thread_ctx Juanlu Herrero
2026-08-14 16:06 ` David Wei
2026-08-14 1:23 ` [PATCH net-next v5 4/6] selftests: net: add multithread client support to iou-zcrx Juanlu Herrero
2026-08-14 16:04 ` David Wei
2026-08-14 1:23 ` [PATCH net-next v5 5/6] selftests: net: add multithread server " Juanlu Herrero
2026-08-14 15:50 ` David Wei
2026-08-14 1:23 ` [PATCH net-next v5 6/6] selftests: net: add rss_multiqueue test variant " Juanlu Herrero
2026-08-14 16:01 ` David Wei
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=20260814012348.46958-1-juanlu@fastmail.com \
--to=juanlu@fastmail.com \
--cc=asml.silence@gmail.com \
--cc=dw@davidwei.uk \
--cc=io-uring@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox