From: John Meneghini <jmeneghi@redhat.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Bryan Gurney <bgurney@redhat.com>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
sagi@grimberg.me, axboe@kernel.dk, mpe@ellerman.id.au,
naveen@kernel.org, maddy@linux.ibm.com, kernel@xen0n.name,
bmarzins@redhat.com
Subject: Re: [PATCH 1/1] nvme: always enable multipath
Date: Fri, 22 Nov 2024 13:29:57 -0500 [thread overview]
Message-ID: <58519c4e-5801-4481-9087-be4f19b218f7@redhat.com> (raw)
In-Reply-To: <Z0DKJWjtrpuy8j_V@kbusch-mbp.dhcp.thefacebook.com>
On 11/22/24 13:15, Keith Busch wrote:> If you want to change the driver to prevent exposing subsequent
> namepsace path block devices when multipath is not enabled, that is
> probably fine.
OK, we'll work on another patch to do this. The plan will be:
When CONFIG_NVME_MULTIPATH=y, you get multipath.c and full support for both nvme multipath (CMIC/NMIC = 1) and non-multipath
devices (CMIC/NMIC=0) devices with 1 /dev entry per namespace.
When CONFIG_NVME_MULTIPATH=n, you get support for non-multipath devices (CMIC/NMIC=0) devices, but multipath devices
(CMIC/NMIC=1) will only expose the first controller/namespace path.
/John
next prev parent reply other threads:[~2024-11-22 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 22:03 [PATCH 1/1] nvme: always enable multipath Bryan Gurney
2024-11-22 6:26 ` Nilay Shroff
2024-11-22 14:10 ` John Meneghini
2024-11-24 13:09 ` Nilay Shroff
2024-11-22 12:09 ` Christoph Hellwig
2024-11-22 15:39 ` Keith Busch
2024-11-22 17:49 ` John Meneghini
2024-11-22 18:15 ` Keith Busch
2024-11-22 18:29 ` John Meneghini [this message]
2024-11-22 17:52 ` John Meneghini
2024-11-22 18:16 ` Keith Busch
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=58519c4e-5801-4481-9087-be4f19b218f7@redhat.com \
--to=jmeneghi@redhat.com \
--cc=axboe@kernel.dk \
--cc=bgurney@redhat.com \
--cc=bmarzins@redhat.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=sagi@grimberg.me \
/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