From: snitzer@redhat.com (Mike Snitzer)
Subject: nvme: make ANA support independent on native nvme multipath
Date: Thu, 8 Nov 2018 11:27:45 -0500 [thread overview]
Message-ID: <20181108162745.GB28854@redhat.com> (raw)
In-Reply-To: <20181108084813.GA3637@lst.de>
On Thu, Nov 08 2018 at 3:48am -0500,
Christoph Hellwig <hch@lst.de> wrote:
> On Mon, Nov 05, 2018@04:41:36PM +0100, Hannes Reinecke wrote:
> > NVMe native multipathing is an implementation detail on the host,
> > and ANA support is actually independent on that.
> > So we shouldn't check for native NVMe multipathing when trying to
> > evaluate whether ANA is supported; not doing so results in the
> > ANA sysfs attributes not to be present when the 'multipath=false'
> > module option is set.
>
> No, we should not enable ANA support without multipathing, as we
> don't want people to rely on any ANA related side effects if multipathing
> is not enabled.
Could you be more specific?
Do you have an example side-effect that you hold to be problematic?
As you can imagine I've long hoped for ANA to be decoupled from
multipathing. Would welcome your throughts on why this is "bad".
Mike
next prev parent reply other threads:[~2018-11-08 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 15:41 [PATCH] nvme: make ANA support independent on native nvme multipath Hannes Reinecke
2018-11-07 2:54 ` Sagi Grimberg
2018-11-08 8:48 ` Christoph Hellwig
2018-11-08 16:27 ` Mike Snitzer [this message]
2018-11-08 16:24 ` 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=20181108162745.GB28854@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).