From: Daniel Wagner <dwagner@suse.de>
To: linux-nvme@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Hannes Reinecke <hare@suse.de>, Daniel Wagner <dwagner@suse.de>
Subject: [RFC v2 0/3] nvme: add csi, ms and nuse to sysfs
Date: Fri, 1 Dec 2023 10:27:32 +0100 [thread overview]
Message-ID: <20231201092735.28592-1-dwagner@suse.de> (raw)
I've moved all ns id info to nvms_ns_head in this version as we discussed in v1
(hope I understood it right). The change was pretty much straightforward except for
nvme_mpath_clear_current_path
nvme_mpath_revalidate_paths
nvme_failover_req
where there is need to access a nvme_ns pointer again. I've tested this change
with the nvme-pci and nvme-tcp transport so far.
Thanks,
Daniel
libnvme changes:
https://github.com/igaw/libnvme/tree/tree-no-cmd
changes:
v2:
- moved ns id data to nvme_ns_head
- dropped ds, nsze
v1:
- initial version
- https://lore.kernel.org/linux-nvme/20231127103208.25748-1-dwagner@suse.de/
Daniel Wagner (3):
nvme: lookup ctrl from request instead from namespace
nvme: move ns id info to struct nvme_ns_head
nvme: add csi, ms and nuse to sysfs
drivers/nvme/host/apple.c | 4 +-
drivers/nvme/host/core.c | 191 +++++++++++++++++----------------
drivers/nvme/host/fc.c | 4 +-
drivers/nvme/host/ioctl.c | 20 ++--
drivers/nvme/host/multipath.c | 40 +++----
drivers/nvme/host/nvme.h | 57 +++++-----
drivers/nvme/host/rdma.c | 10 +-
drivers/nvme/host/sysfs.c | 24 +++++
drivers/nvme/host/tcp.c | 8 +-
drivers/nvme/host/zns.c | 30 +++---
drivers/nvme/target/loop.c | 4 +-
drivers/nvme/target/passthru.c | 8 +-
12 files changed, 216 insertions(+), 184 deletions(-)
--
2.43.0
next reply other threads:[~2023-12-01 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 9:27 Daniel Wagner [this message]
2023-12-01 9:27 ` [RFC v2 1/3] nvme: lookup ctrl from request instead from namespace Daniel Wagner
2023-12-04 7:46 ` Christoph Hellwig
2023-12-04 8:24 ` Sagi Grimberg
2023-12-01 9:27 ` [RFC v2 2/3] nvme: move ns id info to struct nvme_ns_head Daniel Wagner
2023-12-04 7:51 ` Christoph Hellwig
2023-12-04 10:41 ` Daniel Wagner
2023-12-04 8:30 ` Sagi Grimberg
2023-12-04 10:56 ` Daniel Wagner
2023-12-01 9:27 ` [RFC v2 3/3] nvme: add csi, ms and nuse to sysfs Daniel Wagner
2023-12-04 8:48 ` Sagi Grimberg
2023-12-05 6:02 ` Chaitanya Kulkarni
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=20231201092735.28592-1-dwagner@suse.de \
--to=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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;
as well as URLs for NNTP newsgroup(s).