From: Saravanan D <saravanand@crusoe.ai>
To: linux-nvme@lists.infradead.org
Cc: kbusch@kernel.org, hch@lst.de, sagi@grimberg.me, axboe@kernel.dk,
nilay@linux.ibm.com, dwagner@suse.de, sgogte@purestorage.com,
hare@kernel.org, hare@suse.de, linux-kernel@vger.kernel.org,
iyamahata@crusoe.ai, kiyer@crusoe.ai, ganbalagane@crusoe.ai,
sjpark@crusoe.ai, bchen@crusoe.ai,
Saravanan D <saravanand@crusoe.ai>
Subject: [PATCH v7 0/2] nvme-tcp: allow setting per-queue io_cpu through sysfs
Date: Wed, 4 Nov 2026 06:06:28 -0800 [thread overview]
Message-ID: <cover.1793800758.git.saravanand@crusoe.ai> (raw)
On hosts that partition their CPUs after connect time, the connect
time io_cpu selection can place a queue's socket work on CPUs owned by
another workload. This series lets a control plane set each queue's
io_cpu through /sys/class/nvme/nvmeX/queues/<qid>/. Patch 1 adds the
core helpers, patch 2 the nvme-tcp attributes.
Changes since v6 [1]:
- nvme-core now owns the queues directory. A transport lists its queue
attributes in the new queue_attr_groups member of struct
nvme_ctrl_ops, nvme_add_ctrl() creates the directory for it, and
nvme_uninit_ctrl() removes it through the new
nvme_queue_dir_destroy() helper (Nilay).
- Rebased onto the current nvme-7.4.
A blktests patch, nvme/077, covers the interface and follows in this
thread.
[1] https://lore.kernel.org/linux-nvme/20261023230426.6425-1-saravanand@crusoe.ai/
Saravanan D (2):
nvme: add per-queue sysfs directories
nvme-tcp: allow setting per-queue io_cpu through sysfs
Documentation/ABI/stable/sysfs-nvme | 31 ++++++
drivers/nvme/host/core.c | 12 ++
drivers/nvme/host/nvme.h | 25 +++++
drivers/nvme/host/sysfs.c | 88 +++++++++++++++
drivers/nvme/host/tcp.c | 167 ++++++++++++++++++++++++----
5 files changed, 303 insertions(+), 20 deletions(-)
base-commit: ca7e6a9a693240f059a0b47726f64a3f0573011a
--
2.56.0
next reply other threads:[~2026-11-04 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 14:06 Saravanan D [this message]
2026-11-04 14:06 ` [PATCH v7 1/2] nvme: add per-queue sysfs directories Saravanan D
2026-11-04 14:17 ` sashiko-bot
2026-11-04 18:51 ` Saravanan D
2026-11-04 17:30 ` Daniel Wagner
2026-11-06 5:23 ` Saravanan D
2026-11-04 14:06 ` [PATCH v7 2/2] nvme-tcp: allow setting per-queue io_cpu through sysfs Saravanan D
2026-11-04 14:07 ` [PATCH blktests] nvme/077: test the per-queue io_cpu sysfs attribute Saravanan D
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=cover.1793800758.git.saravanand@crusoe.ai \
--to=saravanand@crusoe.ai \
--cc=axboe@kernel.dk \
--cc=bchen@crusoe.ai \
--cc=dwagner@suse.de \
--cc=ganbalagane@crusoe.ai \
--cc=hare@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=iyamahata@crusoe.ai \
--cc=kbusch@kernel.org \
--cc=kiyer@crusoe.ai \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=sagi@grimberg.me \
--cc=sgogte@purestorage.com \
--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.