From: Mike Snitzer <snitzer@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <keith.busch@intel.com>,
Sagi Grimberg <sagi@grimberg.me>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
linux-nvme@lists.infradead.org,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCH 4/5] nvme: implement multipath access to nvme subsystems
Date: Mon, 6 Nov 2017 12:03:56 -0500 [thread overview]
Message-ID: <20171106170356.GD25073@redhat.com> (raw)
In-Reply-To: <20171102183034.9320-5-hch@lst.de>
On Thu, Nov 02 2017 at 2:30pm -0400,
Christoph Hellwig <hch@lst.de> wrote:
> This patch adds native multipath support to the nvme driver. For each
> namespace we create only single block device node, which can be used
> to access that namespace through any of the controllers that refer to it.
> The gendisk for each controllers path to the name space still exists
> inside the kernel, but is hidden from userspace. The character device
> nodes are still available on a per-controller basis. A new link from
> the sysfs directory for the subsystem allows to find all controllers
> for a given subsystem.
>
> Currently we will always send I/O to the first available path, this will
> be changed once the NVMe Asynchronous Namespace Access (ANA) TP is
> ratified and implemented, at which point we will look at the ANA state
> for each namespace. Another possibility that was prototyped is to
> use the path that is closes to the submitting NUMA code, which will be
> mostly interesting for PCI, but might also be useful for RDMA or FC
> transports in the future. There is not plan to implement round robin
> or I/O service time path selectors, as those are not scalable with
> the performance rates provided by NVMe.
>
> The multipath device will go away once all paths to it disappear,
> any delay to keep it alive needs to be implemented at the controller
> level.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> drivers/nvme/host/Kconfig | 9 ++
> drivers/nvme/host/Makefile | 1 +
> drivers/nvme/host/core.c | 133 +++++++++++++++++++---
> drivers/nvme/host/multipath.c | 255 ++++++++++++++++++++++++++++++++++++++++++
> drivers/nvme/host/nvme.h | 57 ++++++++++
> 5 files changed, 440 insertions(+), 15 deletions(-)
> create mode 100644 drivers/nvme/host/multipath.c
>
> diff --git a/drivers/nvme/host/Kconfig b/drivers/nvme/host/Kconfig
> index 46d6cb1e03bd..45886800a1df 100644
> --- a/drivers/nvme/host/Kconfig
> +++ b/drivers/nvme/host/Kconfig
> @@ -13,6 +13,15 @@ config BLK_DEV_NVME
> To compile this driver as a module, choose M here: the
> module will be called nvme.
>
> +config NVME_MULTIPATH
> + bool "NVMe multipath support"
> + depends on NVME_CORE
> + ---help---
> + This option enables support for multipath access to NVMe
> + subsystems. If this option is enabled only a single
> + /dev/nvneXnY device will show up for each NVMe namespaces,
> + even if it is accessible through multiple controllers.
> +
> config NVME_FABRICS
> tristate
>
Thanks for adding this, appreciate it.
next prev parent reply other threads:[~2017-11-06 17:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 18:30 nvme multipath support V6 Christoph Hellwig
2017-11-02 18:30 ` [PATCH 1/5] nvme: track subsystems Christoph Hellwig
2017-11-09 11:33 ` Sagi Grimberg
2017-11-09 12:53 ` Christoph Hellwig
2017-11-09 13:01 ` Sagi Grimberg
2017-11-02 18:30 ` [PATCH 2/5] nvme: introduce a nvme_ns_ids structure Christoph Hellwig
2017-11-02 18:30 ` [PATCH 3/5] nvme: track shared namespaces Christoph Hellwig
2017-11-09 11:37 ` Sagi Grimberg
2017-11-09 12:52 ` Christoph Hellwig
2017-11-09 12:59 ` Sagi Grimberg
2017-11-09 13:20 ` Christoph Hellwig
2017-11-09 16:09 ` Sagi Grimberg
2017-11-02 18:30 ` [PATCH 4/5] nvme: implement multipath access to nvme subsystems Christoph Hellwig
2017-11-06 17:03 ` Mike Snitzer [this message]
2017-11-08 8:54 ` Christoph Hellwig
2017-11-08 11:18 ` Hannes Reinecke
2017-11-09 9:13 ` Christoph Hellwig
2017-11-09 15:44 ` Hannes Reinecke
2017-11-09 15:51 ` Christoph Hellwig
2017-11-02 18:30 ` [PATCH 5/5] nvme: also expose the namespace identification sysfs files for mpath nodes Christoph Hellwig
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=20171106170356.GD25073@redhat.com \
--to=snitzer@redhat.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=keith.busch@intel.com \
--cc=linux-block@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).