From: Nilay Shroff <nilay@linux.ibm.com>
To: linux-nvme@lists.infradead.org
Cc: dwagner@suse.de, hare@kernel.org, kbusch@kernel.org, gjoyce@ibm.com
Subject: [PATCH 0/3] libnvme: add support for discovering multipath of a shared ns
Date: Sat, 5 Apr 2025 18:32:46 +0530 [thread overview]
Message-ID: <20250405130255.448345-1-nilay@linux.ibm.com> (raw)
Hi,
Recently released Linux kernel v6.14 added support for easily discovering
multiple paths to a shared NVMe namespace. This multipath information is
exposed to userspace via a new sysfs group attribute named "multipath",
located under /sys/block/<ns-blkdev>/. More details on this functionality
can be found here [1].
This patch series leverages that new functionality to discover multiple paths
to a shared namespace and exposes that information in libnvme so that it can
later be used by nvme-cli.
There are three patches in this series:
The first patch adds support for discovering NVMe paths using the sysfs
"multipath" group attribute.
The second patch adds a new "queue_depth" attribute under the NVMe path object.
The third patch adds a new "numa_nodes" attribute under the NVMe path object.
[1]: https://lore.kernel.org/all/20250112124154.60690-1-nilay@linux.ibm.com/
Nilay Shroff (3):
tree: add support for discovering nvme paths using sysfs multipath
link
tree: add queue-depth attribute for nvme path object
tree: add attribute numa_nodes for NVMe path object
src/libnvme.map | 2 +
src/nvme/filters.c | 6 ++
src/nvme/filters.h | 9 +++
src/nvme/private.h | 11 ++-
src/nvme/tree.c | 184 ++++++++++++++++++++++++++++++++-------------
src/nvme/tree.h | 25 ++++++
6 files changed, 184 insertions(+), 53 deletions(-)
--
2.49.0
next reply other threads:[~2025-04-05 13:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 13:02 Nilay Shroff [this message]
2025-04-05 13:02 ` [PATCH 1/3] tree: add support for discovering nvme paths using sysfs multipath link Nilay Shroff
2025-04-07 7:19 ` Daniel Wagner
2025-04-07 9:36 ` Nilay Shroff
2025-04-07 11:01 ` Daniel Wagner
2025-04-07 13:43 ` Nilay Shroff
2025-04-05 13:02 ` [PATCH 2/3] tree: add queue-depth attribute for nvme path object Nilay Shroff
2025-04-07 7:40 ` Daniel Wagner
2025-04-05 13:02 ` [PATCH 3/3] tree: add attribute numa_nodes for NVMe " Nilay Shroff
2025-04-07 7:44 ` Daniel Wagner
2025-04-07 9:59 ` Nilay Shroff
2025-04-07 11:10 ` Daniel Wagner
2025-04-07 14:19 ` Nilay Shroff
2025-04-07 15:19 ` Daniel Wagner
2025-04-08 5:58 ` Hannes Reinecke
2025-04-08 11:42 ` Daniel Wagner
2025-04-08 11:48 ` Hannes Reinecke
2025-04-09 9:38 ` Nilay Shroff
2025-04-09 11:36 ` Daniel Wagner
2025-04-05 16:15 ` [PATCH 0/3] libnvme: add support for discovering multipath of a shared ns Nilay Shroff
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=20250405130255.448345-1-nilay@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=dwagner@suse.de \
--cc=gjoyce@ibm.com \
--cc=hare@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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 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.