From: patchwork-bot+netdevbpf@kernel.org
To: Juanlu Herrero <juanlu@fastmail.com>
Cc: dw@davidwei.uk, netdev@vger.kernel.org, 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
Subject: Re: [PATCH net-next v7 0/6] selftests: net: make iou-zcrx tests multithreaded
Date: Tue, 15 Sep 2026 02:30:08 +0000 [thread overview]
Message-ID: <178943940862.1322157.740585578841979975.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260909-iou-zcrx-v7-0-6b5d48a2a922@fastmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 09 Sep 2026 14:51:22 -0500 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [net-next,v7,1/6] selftests: net: fix get_refill_ring_size() to use its local variable
https://git.kernel.org/netdev/net-next/c/649936a0daaa
- [net-next,v7,2/6] selftests: net: remove unused variable in process_recvzc()
https://git.kernel.org/netdev/net-next/c/3fb289238244
- [net-next,v7,3/6] selftests: net: refactor server state into struct thread_ctx
https://git.kernel.org/netdev/net-next/c/72ac4f0c5398
- [net-next,v7,4/6] selftests: net: add multithread client support to iou-zcrx
https://git.kernel.org/netdev/net-next/c/280189574629
- [net-next,v7,5/6] selftests: net: add multithread server support to iou-zcrx
https://git.kernel.org/netdev/net-next/c/5d3416ebe555
- [net-next,v7,6/6] selftests: net: add rss_multiqueue test variant to iou-zcrx
https://git.kernel.org/netdev/net-next/c/9814d2fa8742
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-15 2:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 19:51 Juanlu Herrero
2026-09-09 19:51 ` [PATCH net-next v7 1/6] selftests: net: fix get_refill_ring_size() to use its local variable Juanlu Herrero
2026-09-09 19:51 ` [PATCH net-next v7 2/6] selftests: net: remove unused variable in process_recvzc() Juanlu Herrero
2026-09-09 19:51 ` [PATCH net-next v7 3/6] selftests: net: refactor server state into struct thread_ctx Juanlu Herrero
2026-09-09 19:51 ` [PATCH net-next v7 4/6] selftests: net: add multithread client support to iou-zcrx Juanlu Herrero
2026-09-09 19:51 ` [PATCH net-next v7 5/6] selftests: net: add multithread server " Juanlu Herrero
2026-09-09 19:51 ` [PATCH net-next v7 6/6] selftests: net: add rss_multiqueue test variant " Juanlu Herrero
2026-09-15 2:30 ` patchwork-bot+netdevbpf [this message]
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=178943940862.1322157.740585578841979975.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=asml.silence@gmail.com \
--cc=dw@davidwei.uk \
--cc=io-uring@vger.kernel.org \
--cc=juanlu@fastmail.com \
--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
all inboxes | Powered by JetHome®