From: Christoph Hellwig <hch@infradead.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
bvanassche@acm.org, yi.zhang@redhat.com, sagi@grimberg.me,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: can't run nvme-mp blktests
Date: Thu, 14 Apr 2022 22:22:08 -0700 [thread overview]
Message-ID: <YlkBAKBec6BULlE+@infradead.org> (raw)
In-Reply-To: <YlcSiszuNqVZMsb5@bombadil.infradead.org>
On Wed, Apr 13, 2022 at 11:12:26AM -0700, Luis Chamberlain wrote:
> OK so CONFIG_NVME_MULTIPATH will be nuked, but the module parameter
> will remain, and if the module parameter is used with multipath=N you'll
> end up with a single namespace once the phase out of
> CONFIG_NVME_MULTIPATH is complete.
The other way around. The plan is that CONFIG_NVME_MULTIPATH will
stay around forever - for deeply embedded devices that only have
a soldered on or sd-card nvme device with a single path there is no
need to carry the multipathing code around. But the code to support
multiple controllers in a subsystem without CONFIG_NVME_MULTIPATH
will go away.
next prev parent reply other threads:[~2022-04-15 5:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 0:24 can't run nvme-mp blktests Luis Chamberlain
2022-04-13 3:02 ` Yi Zhang
2022-04-13 17:38 ` Luis Chamberlain
2022-04-13 4:53 ` Christoph Hellwig
2022-04-13 17:38 ` Luis Chamberlain
2022-04-13 17:41 ` Christoph Hellwig
2022-04-13 18:12 ` Luis Chamberlain
2022-04-15 5:22 ` Christoph Hellwig [this message]
2022-04-13 22:46 ` Bart Van Assche
2022-04-15 5:20 ` Christoph Hellwig
2022-04-15 5:58 ` Chaitanya Kulkarni
2022-04-15 17:59 ` Luis Chamberlain
2022-04-15 18:09 ` Bart Van Assche
2022-04-20 10:36 ` Hannes Reinecke
2022-04-21 17:56 ` Luis Chamberlain
2022-04-15 18:06 ` Bart Van Assche
2022-04-20 10:29 ` Hannes Reinecke
2022-04-13 5:53 ` Bart Van Assche
2022-04-13 18:08 ` Luis Chamberlain
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=YlkBAKBec6BULlE+@infradead.org \
--to=hch@infradead.org \
--cc=bvanassche@acm.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mcgrof@kernel.org \
--cc=sagi@grimberg.me \
--cc=yi.zhang@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.