From: snitzer@redhat.com (Mike Snitzer)
Subject: [LSF/MM TOPIC] update NVMe multipath to conditionally claim controllers
Date: Mon, 29 Jan 2018 16:17:23 -0500 [thread overview]
Message-ID: <20180129211722.GB5744@redhat.com> (raw)
I'd like to have the same Linux kernel be able to use either NVMe's
native multipath or DM multipath.
Should be relatively simple to filter which controllers can/cannot be
claimed by NVMe multipathing (without having to resort to the big hammer
of CONFIG_NVME_MULTIPATH).
I'd like to understand what is the preferred disposition of the filter
list (black or white)? I assume having a blacklist would be more
inkeeping with Christoph's desire for NVMe to be the default for NVMe
multipathing. But that disposition aside, not sure if there are other
issues that should influence implementing more flexible use of NVMe
resources.
Thanks,
Mike
next reply other threads:[~2018-01-29 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 21:17 Mike Snitzer [this message]
2018-01-30 15:04 ` [dm-devel] [LSF/MM TOPIC] update NVMe multipath to conditionally claim controllers Hannes Reinecke
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=20180129211722.GB5744@redhat.com \
--to=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;
as well as URLs for NNTP newsgroup(s).