From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Saravanan D <saravanand@crusoe.ai>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
dwagner@suse.de, hare@suse.de, nilay@linux.ibm.com,
sagi@grimberg.me, kbusch@kernel.org, iyamahata@crusoe.ai,
kiyer@crusoe.ai, ganbalagane@crusoe.ai, sjpark@crusoe.ai,
bchen@crusoe.ai
Subject: Re: [PATCH blktests] nvme/075: test the per-queue io_cpu sysfs attribute
Date: Thu, 29 Oct 2026 20:50:39 +0900 [thread overview]
Message-ID: <auMw5Gxg6toa8GD2@shinmob> (raw)
In-Reply-To: <20261023230809.7869-1-saravanand@crusoe.ai>
On Oct 23, 2026 / 16:08, Saravanan D wrote:
> nvme-tcp exposes /sys/class/nvme/nvmeX/queues/<qid>/io_cpu and managed,
> so a control plane can choose the CPU that runs each I/O queue's socket
> work [1]. Test that
>
> - io_cpu reads back a written CPU and rejects invalid values
> - managed is read only and turns 0 once io_cpu is written
> - an assignment survives a controller reset
> - the queue directories follow the queue count as attr_qid_max
> shrinks and grows it
> - removing the controller while io_cpu is written completes
>
> The test skips when the kernel does not have the attribute.
>
> [1] https://lore.kernel.org/linux-nvme/20261018010059.83120-1-saravanand@crusoe.ai/
>
> Assisted-by: Claude:claude-opus-5-5 [Claude Code]
> Signed-off-by: Saravanan D <saravanand@crusoe.ai>
> ---
> This tests the kernel series in the parent thread, which is under
> review on linux-nvme.
Thanks for the patch. The patch content looks good to me. I applied the kernel
series [1] on top of the current Linus master branch, and confirmed this new
test case passes. Good.
I'll wait for the kernel series get settled. I expect the kernel series will be
revised a few more times, and this blktests patch will need to adjust to it,
probably.
prev parent reply other threads:[~2026-10-29 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 23:04 [PATCH v6 0/2] nvme-tcp: allow setting per-queue io_cpu through sysfs Saravanan D
2026-10-23 23:04 ` [PATCH v6 1/2] nvme: add per-queue sysfs directories Saravanan D
2026-10-23 23:04 ` [PATCH v6 2/2] nvme-tcp: allow setting per-queue io_cpu through sysfs Saravanan D
2026-10-23 23:08 ` [PATCH blktests] nvme/075: test the per-queue io_cpu sysfs attribute Saravanan D
2026-10-29 11:50 ` Shin'ichiro Kawasaki [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=auMw5Gxg6toa8GD2@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=bchen@crusoe.ai \
--cc=dwagner@suse.de \
--cc=ganbalagane@crusoe.ai \
--cc=hare@suse.de \
--cc=iyamahata@crusoe.ai \
--cc=kbusch@kernel.org \
--cc=kiyer@crusoe.ai \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=sagi@grimberg.me \
--cc=saravanand@crusoe.ai \
--cc=sjpark@crusoe.ai \
/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.