All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 8/9] nvme: implement multipath access to nvme subsystems
Date: Mon, 25 Sep 2017 10:18:10 -0600	[thread overview]
Message-ID: <20170925161810.GD8463@localhost.localdomain> (raw)
In-Reply-To: <20170925134031.10548-9-hch@lst.de>

On Mon, Sep 25, 2017 at 03:40:30PM +0200, Christoph Hellwig wrote:
> This patch adds initial multipath support to the nvme driver.  For each
> namespace we create a new block device node, which can be used to access
> that namespace through any of the controllers that refer to it.
> 
> 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.
> 
> The new block devices nodes for multipath access will show up as
> 
> 	/dev/nvm-subXnZ
> 
> where X is the local instance number of the subsystems, and Z is the index
> for the namespace.
> 
> To get persistent devices names the following lines can be added to
> /lib/udev/rules.d/60-persistent-storage.rules:
> 
> ---------------------------------- snip ----------------------------------
> KERNEL=="nvm-sub*[0-9]n*[0-9]", ATTR{wwid}=="?*", SYMLINK+="disk/by-id/nvme-sub-$attr{wwid}"
> KERNEL=="nvm-sub*[0-9]n*[0-9]p*[0-9]", ENV{DEVTYPE}=="partition", ATTRS{wwid}=="?*", SYMLINK+="disk/by-id/nvme-sub-$attr{wwid}-part%n"
> KERNEL=="nvm-sub*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{wwid}=="?*", ENV{ID_WWN}="$attr{wwid}"
> ---------------------------------- snip ----------------------------------
> 
> Note that these create the new persistent names.  Overriding the existing
> nvme ones would be nicer, but while that works for the first path, the
> normal rule will override it again for each subsequent path.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Looks good.

Reviewed-by: Keith Busch <keith.busch@intel.com>

WARNING: multiple messages have this Message-ID (diff)
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 8/9] nvme: implement multipath access to nvme subsystems
Date: Mon, 25 Sep 2017 10:18:10 -0600	[thread overview]
Message-ID: <20170925161810.GD8463@localhost.localdomain> (raw)
In-Reply-To: <20170925134031.10548-9-hch@lst.de>

On Mon, Sep 25, 2017@03:40:30PM +0200, Christoph Hellwig wrote:
> This patch adds initial multipath support to the nvme driver.  For each
> namespace we create a new block device node, which can be used to access
> that namespace through any of the controllers that refer to it.
> 
> 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.
> 
> The new block devices nodes for multipath access will show up as
> 
> 	/dev/nvm-subXnZ
> 
> where X is the local instance number of the subsystems, and Z is the index
> for the namespace.
> 
> To get persistent devices names the following lines can be added to
> /lib/udev/rules.d/60-persistent-storage.rules:
> 
> ---------------------------------- snip ----------------------------------
> KERNEL=="nvm-sub*[0-9]n*[0-9]", ATTR{wwid}=="?*", SYMLINK+="disk/by-id/nvme-sub-$attr{wwid}"
> KERNEL=="nvm-sub*[0-9]n*[0-9]p*[0-9]", ENV{DEVTYPE}=="partition", ATTRS{wwid}=="?*", SYMLINK+="disk/by-id/nvme-sub-$attr{wwid}-part%n"
> KERNEL=="nvm-sub*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{wwid}=="?*", ENV{ID_WWN}="$attr{wwid}"
> ---------------------------------- snip ----------------------------------
> 
> Note that these create the new persistent names.  Overriding the existing
> nvme ones would be nicer, but while that works for the first path, the
> normal rule will override it again for each subsequent path.
> 
> Signed-off-by: Christoph Hellwig <hch at lst.de>

Looks good.

Reviewed-by: Keith Busch <keith.busch at intel.com>

  parent reply	other threads:[~2017-09-25 16:18 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 13:40 nvme multipath support V3 Christoph Hellwig
2017-09-25 13:40 ` Christoph Hellwig
2017-09-25 13:40 ` [PATCH 1/9] block: move REQ_NOWAIT Christoph Hellwig
2017-09-25 13:40   ` Christoph Hellwig
2017-10-11 11:51   ` Sagi Grimberg
2017-10-11 11:51     ` Sagi Grimberg
2017-09-25 13:40 ` [PATCH 2/9] block: add REQ_DRV bit Christoph Hellwig
2017-09-25 13:40   ` Christoph Hellwig
2017-10-11 11:51   ` Sagi Grimberg
2017-10-11 11:51     ` Sagi Grimberg
2017-09-25 13:40 ` [PATCH 3/9] block: provide a direct_make_request helper Christoph Hellwig
2017-09-25 13:40   ` Christoph Hellwig
2017-10-11 11:54   ` Sagi Grimberg
2017-10-11 11:54     ` Sagi Grimberg
2017-09-25 13:40 ` [PATCH 4/9] block: add a blk_steal_bios helper Christoph Hellwig
2017-09-25 13:40   ` Christoph Hellwig
2017-09-25 13:40 ` [PATCH 5/9] nvme: track subsystems Christoph Hellwig
2017-09-25 13:40   ` Christoph Hellwig
2017-09-25 16:07   ` Keith Busch
2017-09-25 16:07     ` Keith Busch
2017-10-11 11:57   ` Sagi Grimberg
2017-10-11 11:57     ` Sagi Grimberg
2017-10-18 10:12     ` Christoph Hellwig
2017-10-18 10:12       ` Christoph Hellwig
2017-10-18 11:16       ` Sagi Grimberg
2017-10-18 11:16         ` Sagi Grimberg
2017-09-25 13:40 ` [PATCH 6/9] nvme: introduce a nvme_ns_ids structure Christoph Hellwig
2017-09-25 13:40   ` Christoph Hellwig
2017-09-25 16:08   ` Keith Busch
2017-09-25 16:08     ` Keith Busch
2017-10-11 11:59   ` Sagi Grimberg
2017-10-11 11:59     ` Sagi Grimberg
2017-09-25 13:40 ` [PATCH 7/9] nvme: track shared namespaces Christoph Hellwig
2017-09-25 13:40   ` Christoph Hellwig
2017-09-25 16:11   ` Keith Busch
2017-09-25 16:11     ` Keith Busch
2017-09-25 16:19     ` Christoph Hellwig
2017-09-25 16:19       ` Christoph Hellwig
2017-10-11 12:04   ` Sagi Grimberg
2017-10-11 12:04     ` Sagi Grimberg
2017-10-18 10:15     ` Christoph Hellwig
2017-10-18 10:15       ` Christoph Hellwig
2017-09-25 13:40 ` [PATCH 8/9] nvme: implement multipath access to nvme subsystems Christoph Hellwig
2017-09-25 13:40   ` Christoph Hellwig
2017-09-25 13:47   ` Hannes Reinecke
2017-09-25 13:47     ` Hannes Reinecke
2017-09-25 13:50     ` Christoph Hellwig
2017-09-25 13:50       ` Christoph Hellwig
2017-09-25 14:05       ` Hannes Reinecke
2017-09-25 14:05         ` Hannes Reinecke
2017-09-25 14:45         ` Keith Busch
2017-09-25 14:45           ` Keith Busch
2017-09-25 15:07         ` Christoph Hellwig
2017-09-25 15:07           ` Christoph Hellwig
2017-09-25 16:18   ` Keith Busch [this message]
2017-09-25 16:18     ` Keith Busch
2017-09-28 15:53   ` Keith Busch
2017-09-28 15:53     ` Keith Busch
2017-09-29 14:21     ` Tony Yang
2017-09-29 14:21       ` Tony Yang
2017-10-01  8:07       ` Christoph Hellwig
2017-10-01  8:07         ` Christoph Hellwig
2017-09-30 19:37     ` Johannes Thumshirn
2017-09-30 19:37       ` Johannes Thumshirn
2017-10-01  8:07       ` Christoph Hellwig
2017-10-01  8:07         ` Christoph Hellwig
2017-10-02  6:19       ` Hannes Reinecke
2017-10-02  6:19         ` Hannes Reinecke
2017-10-11 12:24   ` Sagi Grimberg
2017-10-11 12:24     ` Sagi Grimberg
2017-09-25 13:40 ` [PATCH 9/9] nvme: also expose the namespace identification sysfs files for mpath nodes Christoph Hellwig
2017-09-25 13:40   ` Christoph Hellwig
2017-09-25 16:19   ` Keith Busch
2017-09-25 16:19     ` Keith Busch

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=20170925161810.GD8463@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --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 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.