From: Nilay Shroff <nilay@linux.ibm.com>
To: linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>,
Daniel Wagner <dwagner@suse.de>
Cc: kbusch@kernel.org, gjoyce@ibm.com
Subject: Re: [PATCHv3 0/4] libnvme: add support for discovering multipath of a shared ns
Date: Tue, 13 May 2025 16:58:13 +0530 [thread overview]
Message-ID: <81e2ffe5-5e71-49c1-a914-7660a9712e92@linux.ibm.com> (raw)
In-Reply-To: <20250425185617.1242994-1-nilay@linux.ibm.com>
Hi Daniel, Hannes,
A gentle ping... Do you have any further comment for this patchset?
Thanks,
--Nilay
On 4/26/25 12:26 AM, Nilay Shroff wrote:
> Hi,
>
> Recently released Linux kernel v6.15-rc1 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 four 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.
> The fourth patch extends the sysfs tree dump test to validate multipath link
> support
>
> [1]: https://lore.kernel.org/all/20250112124154.60690-1-nilay@linux.ibm.com/
>
> Changes from v2:
> - Modified queue_depth get attribure function to always return the latest
> value insteda of cached value (Hannes Reinecke)
>
> Changes from v1:
> - Fixed kernel version typo in the cover letter and commit
> - Updated the commit in first patch to explain the change in some
> detail (Daniel Wagner)
> - Added fourth patch to validate changes (Daniel Wagner)
>
>
> Nilay Shroff (4):
> 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
> test: extend sysfs tree dump test
>
> src/libnvme.map | 2 +
> src/nvme/filters.c | 6 +
> src/nvme/filters.h | 9 ++
> src/nvme/json.c | 90 +++++++++++++--
> src/nvme/private.h | 11 +-
> src/nvme/tree.c | 191 ++++++++++++++++++++++---------
> src/nvme/tree.h | 25 ++++
> test/sysfs/data/tree-pcie.out | 53 +++++++--
> test/sysfs/data/tree-pcie.tar.xz | Bin 19712 -> 12656 bytes
> 9 files changed, 315 insertions(+), 72 deletions(-)
>
next prev parent reply other threads:[~2025-05-13 11:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 18:56 [PATCHv3 0/4] libnvme: add support for discovering multipath of a shared ns Nilay Shroff
2025-04-25 18:56 ` [PATCHv3 1/4] tree: add support for discovering nvme paths using sysfs multipath link Nilay Shroff
2025-04-25 18:56 ` [PATCHv3 2/4] tree: add queue-depth attribute for nvme path object Nilay Shroff
2025-04-25 18:56 ` [PATCHv3 3/4] tree: add attribute numa_nodes for NVMe " Nilay Shroff
2025-04-25 18:56 ` [PATCHv3 4/4] test: extend sysfs tree dump test Nilay Shroff
2025-05-13 11:28 ` Nilay Shroff [this message]
2025-06-04 14:47 ` [PATCHv3 0/4] libnvme: add support for discovering multipath of a shared ns Daniel Wagner
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=81e2ffe5-5e71-49c1-a914-7660a9712e92@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=dwagner@suse.de \
--cc=gjoyce@ibm.com \
--cc=hare@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox