From: Keith Busch <keith.busch@intel.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Ming Lin <mlin@kernel.org>,
device-mapper development <dm-devel@redhat.com>,
linux-nvme@lists.infradead.org
Subject: Re: NVMeoF multi-path setup
Date: Thu, 30 Jun 2016 19:14:55 -0400 [thread overview]
Message-ID: <20160630231454.GC18890@localhost.localdomain> (raw)
In-Reply-To: <20160630225207.GB22293@redhat.com>
On Thu, Jun 30, 2016 at 06:52:07PM -0400, Mike Snitzer wrote:
> AFAIK, hch had Intel disable that by default in the hopes of avoiding
> people having dm-multipath "just work" with NVMeoF. (Makes me wonder
> what other unpleasant unilateral decisions were made because some
> non-existant NVMe specific multipath capabilities would be forthcoming
> but I digress).
For the record, Intel was okay with making SCSI a separate config option,
but I was pretty clear about our wish to let it default to 'Y', which
didn't happen. :)
To be fair, NVMe's SCSI translation is a bit of a kludge, and we have
better ways to get device identification now. Specifically, the block
device provides 'ATTR{wwid}' available to all NVMe namespaces in existing
kernel releases.
WARNING: multiple messages have this Message-ID (diff)
From: keith.busch@intel.com (Keith Busch)
Subject: NVMeoF multi-path setup
Date: Thu, 30 Jun 2016 19:14:55 -0400 [thread overview]
Message-ID: <20160630231454.GC18890@localhost.localdomain> (raw)
In-Reply-To: <20160630225207.GB22293@redhat.com>
On Thu, Jun 30, 2016@06:52:07PM -0400, Mike Snitzer wrote:
> AFAIK, hch had Intel disable that by default in the hopes of avoiding
> people having dm-multipath "just work" with NVMeoF. (Makes me wonder
> what other unpleasant unilateral decisions were made because some
> non-existant NVMe specific multipath capabilities would be forthcoming
> but I digress).
For the record, Intel was okay with making SCSI a separate config option,
but I was pretty clear about our wish to let it default to 'Y', which
didn't happen. :)
To be fair, NVMe's SCSI translation is a bit of a kludge, and we have
better ways to get device identification now. Specifically, the block
device provides 'ATTR{wwid}' available to all NVMe namespaces in existing
kernel releases.
next prev parent reply other threads:[~2016-06-30 23:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 21:08 NVMeoF multi-path setup Ming Lin
2016-06-30 21:08 ` Ming Lin
2016-06-30 21:57 ` Ming Lin
2016-06-30 21:57 ` Ming Lin
2016-06-30 22:19 ` Ming Lin
2016-06-30 22:19 ` Ming Lin
2016-06-30 22:52 ` Mike Snitzer
2016-06-30 22:52 ` Mike Snitzer
2016-06-30 22:57 ` Mike Snitzer
2016-06-30 22:57 ` Mike Snitzer
2016-06-30 23:14 ` Keith Busch [this message]
2016-06-30 23:14 ` Keith Busch
2016-07-13 10:19 ` Sagi Grimberg
2016-07-13 10:19 ` [dm-devel] " Sagi Grimberg
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=20160630231454.GC18890@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=dm-devel@redhat.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mlin@kernel.org \
--cc=snitzer@redhat.com \
/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.