From: Christoph Hellwig <hch@lst.de>
To: Bryan Gurney <bgurney@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
kbusch@kernel.org, hch@lst.de, sagi@grimberg.me, axboe@kernel.dk,
mpe@ellerman.id.au, naveen@kernel.org, maddy@linux.ibm.com,
kernel@xen0n.name, jmeneghi@redhat.com, bmarzins@redhat.com
Subject: Re: [PATCH 1/1] nvme: always enable multipath
Date: Fri, 22 Nov 2024 13:09:25 +0100 [thread overview]
Message-ID: <20241122120925.GA25817@lst.de> (raw)
In-Reply-To: <20241121220321.40616-1-bgurney@redhat.com>
On Thu, Nov 21, 2024 at 05:03:21PM -0500, Bryan Gurney wrote:
> Since device-mapper multipath will no longer be operating on NVMe
> devices, there is no longer a need to set CONFIG_NVME_MULTIPATH=n.
>
> Always enable NVMe multipath, remove CONFIG_NVME_MULTIPATH, and use
> the code paths that would be used if CONFIG_NVME_MULTIPATH=y.
As mentioned last round not having to build the not tiny multipath
code for embedded systems and other small builds that never require
multipathing still seems like a sensible idea.
next prev parent reply other threads:[~2024-11-22 12:09 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 [this message]
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
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=20241122120925.GA25817@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bgurney@redhat.com \
--cc=bmarzins@redhat.com \
--cc=jmeneghi@redhat.com \
--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