From: "hch@infradead.org" <hch@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Keith Busch <keith.busch@intel.com>,
"hch@infradead.org" <hch@infradead.org>,
Bart Van Assche <Bart.VanAssche@sandisk.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.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:04:20 -0800 [thread overview]
Message-ID: <20170217090420.GA29629@infradead.org> (raw)
In-Reply-To: <20170216182129.GC12678@redhat.com>
On Thu, Feb 16, 2017 at 01:21:29PM -0500, Mike Snitzer wrote:
> multipath-tools has tables that specify all the defaults for a given
> target backend. NVMe will just be yet another.
No, if we get things right it won't. ALUA already got rid of most
of the parameter people would have to set under normal conditions,
and I plan to make sure the NVMe equivalent will do it for all
parameters. I am active in the NVMe working group and will do my
best to get there. There's a few others folks here that are more or
less active there as well (Keith, Martin, Jens for example), so I
think we have a chance.
That beeing said Keith is right that we'll always have odd setups
where we need to overrid things, and we will have to provide tunables
for that. It's no different from any other kernel subsystem in that.
WARNING: multiple messages have this Message-ID (diff)
From: hch@infradead.org (hch@infradead.org)
Subject: [dm-devel] hch's native NVMe multipathing [was: Re: [PATCH 1/2] Don't blacklist nvme]
Date: Fri, 17 Feb 2017 01:04:20 -0800 [thread overview]
Message-ID: <20170217090420.GA29629@infradead.org> (raw)
In-Reply-To: <20170216182129.GC12678@redhat.com>
On Thu, Feb 16, 2017@01:21:29PM -0500, Mike Snitzer wrote:
> multipath-tools has tables that specify all the defaults for a given
> target backend. NVMe will just be yet another.
No, if we get things right it won't. ALUA already got rid of most
of the parameter people would have to set under normal conditions,
and I plan to make sure the NVMe equivalent will do it for all
parameters. I am active in the NVMe working group and will do my
best to get there. There's a few others folks here that are more or
less active there as well (Keith, Martin, Jens for example), so I
think we have a chance.
That beeing said Keith is right that we'll always have odd setups
where we need to overrid things, and we will have to provide tunables
for that. It's no different from any other kernel subsystem in that.
next prev parent reply other threads:[~2017-02-17 9:04 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 21:19 [PATCH 1/2] Don't blacklist nvme Keith Busch
2017-02-14 21:19 ` [PATCH 2/2] Fill NVMe specific path info Keith Busch
2017-02-20 17:57 ` Benjamin Marzinski
2017-02-21 21:06 ` Keith Busch
2017-02-14 21:35 ` [PATCH 1/2] Don't blacklist nvme Bart Van Assche
2017-02-14 23:00 ` Keith Busch
2017-02-15 14:57 ` Christoph Hellwig
2017-02-15 17:24 ` Keith Busch
2017-02-16 1:58 ` Mike Snitzer
2017-02-16 2:01 ` Mike Snitzer
2017-02-16 2:35 ` Mike Snitzer
2017-02-15 14:56 ` Christoph Hellwig
2017-02-16 2:53 ` hch's native NVMe multipathing [was: Re: [PATCH 1/2] Don't blacklist nvme] Mike Snitzer
2017-02-16 2:53 ` Mike Snitzer
2017-02-16 5:00 ` [dm-devel] " Bart Van Assche
2017-02-16 5:00 ` Bart Van Assche
2017-02-16 12:37 ` Mike Snitzer
2017-02-16 12:37 ` Mike Snitzer
2017-02-16 19:46 ` Bart Van Assche
2017-02-16 19:46 ` Bart Van Assche
2017-02-16 20:23 ` Mike Snitzer
2017-02-16 20:23 ` Mike Snitzer
2017-02-16 20:58 ` Bart Van Assche
2017-02-16 20:58 ` Bart Van Assche
2017-02-16 14:26 ` [dm-devel] " Christoph Hellwig
2017-02-16 14:26 ` Christoph Hellwig
2017-02-16 15:13 ` Mike Snitzer
2017-02-16 15:13 ` Mike Snitzer
2017-02-16 17:38 ` Keith Busch
2017-02-16 17:38 ` Keith Busch
2017-02-16 17:37 ` Bart Van Assche
2017-02-16 17:37 ` Bart Van Assche
2017-02-16 18:07 ` Keith Busch
2017-02-16 18:07 ` Keith Busch
2017-02-16 18:21 ` Mike Snitzer
2017-02-16 18:21 ` Mike Snitzer
2017-02-16 20:40 ` Keith Busch
2017-02-16 20:40 ` Keith Busch
2017-02-17 9:04 ` hch [this message]
2017-02-17 9:04 ` [dm-devel] " hch
2017-02-17 14:43 ` Mike Snitzer
2017-02-17 14:43 ` Mike Snitzer
2017-02-16 18:05 ` Sagi Grimberg
2017-02-16 18:05 ` Sagi Grimberg
2017-02-17 9:05 ` [dm-devel] " Christoph Hellwig
2017-02-17 9:05 ` Christoph Hellwig
2017-02-17 14:37 ` Mike Snitzer
2017-02-17 14:37 ` Mike Snitzer
2017-02-17 9:33 ` [dm-devel] " Christoph Hellwig
2017-02-17 9:33 ` Christoph Hellwig
2017-02-17 14:32 ` Mike Snitzer
2017-02-17 14:32 ` Mike Snitzer
2017-02-20 18:17 ` [PATCH 1/2] Don't blacklist nvme Benjamin Marzinski
2017-02-20 14:14 ` Mike Snitzer
2017-02-27 5:37 ` Christophe Varoqui
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=20170217090420.GA29629@infradead.org \
--to=hch@infradead.org \
--cc=Bart.VanAssche@sandisk.com \
--cc=dm-devel@redhat.com \
--cc=keith.busch@intel.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.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.