From: Christoph Hellwig <hch@infradead.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Mike Snitzer <snitzer@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Keith Busch <keith.busch@intel.com>,
dm-devel@redhat.com, linux-nvme@lists.infradead.org,
linux-scsi@vger.kernel.org
Subject: Re: [dm-devel] hch's native NVMe multipathing [was: Re: [PATCH 1/2] Don't blacklist nvme]
Date: Fri, 17 Feb 2017 01:05:45 -0800 [thread overview]
Message-ID: <20170217090545.GB29629@infradead.org> (raw)
In-Reply-To: <8ce207d3-844a-8190-9644-1f54dbd7d56b@grimberg.me>
On Thu, Feb 16, 2017 at 08:05:36PM +0200, Sagi Grimberg wrote:
> I guess one config option that we'd need is multibus vs. failover
> which are used per use-case.
Which fundamentally is a property of the target first, and it should
tell us that. There might be the occasional need for an override,
but certainly not locally maintained tables of targets and their
preferences.
next prev parent reply other threads:[~2017-02-17 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1487107154-24883-1-git-send-email-keith.busch@intel.com>
[not found] ` <941dc20e-47ba-5b9d-5082-a87ff1530cb6@sandisk.com>
[not found] ` <20170214230023.GA1148@localhost.localdomain>
[not found] ` <20170216020146.GA9078@redhat.com>
2017-02-16 2:35 ` [PATCH 1/2] Don't blacklist nvme Mike Snitzer
[not found] ` <20170215145617.GA4241@infradead.org>
[not found] ` <20170216025357.GA9241@redhat.com>
[not found] ` <20170216142621.GA21972@infradead.org>
2017-02-16 15:13 ` hch's native NVMe multipathing [was: Re: [PATCH 1/2] Don't blacklist nvme] Mike Snitzer
2017-02-16 17:38 ` Keith Busch
2017-02-16 17:37 ` Bart Van Assche
2017-02-16 18:07 ` Keith Busch
2017-02-16 18:21 ` Mike Snitzer
2017-02-16 20:40 ` Keith Busch
2017-02-17 9:04 ` [dm-devel] " hch
2017-02-17 14:43 ` Mike Snitzer
2017-02-16 18:05 ` Sagi Grimberg
2017-02-17 9:05 ` Christoph Hellwig [this message]
2017-02-17 14:37 ` Mike Snitzer
2017-02-17 9:33 ` [dm-devel] " Christoph Hellwig
2017-02-17 14:32 ` Mike Snitzer
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=20170217090545.GB29629@infradead.org \
--to=hch@infradead.org \
--cc=dm-devel@redhat.com \
--cc=keith.busch@intel.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sagi@grimberg.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox