From: Christoph Hellwig <hch@lst.de>
To: John Meneghini <jmeneghi@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
kbusch@kernel.org, sagi@grimberg.me, loberman@redhat.com,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
emilne@redhat.com, bgurney@redhat.com
Subject: Re: [PATCH 2/4] nvme-multipath: add the NVME_MULTIPATH_PARAM config option
Date: Wed, 12 Mar 2025 06:19:58 +0100 [thread overview]
Message-ID: <20250312051958.GA11824@lst.de> (raw)
In-Reply-To: <03e7cc64-fafd-405e-a07a-4bc6d0e1d743@redhat.com>
On Tue, Mar 11, 2025 at 10:35:40PM -0400, John Meneghini wrote:
>> What's the point of adding yet another confusing option?
>
> If you'll read the kConfig description, hopefully it's not confusing.
It still is.
> The whole point of this patch series is to remove the core.nvme_mulipath parameter.
Why would a compile time option be preferable over a runtime one?
next prev parent reply other threads:[~2025-03-12 5:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 3:25 [PATCH 0/4] nvme: make core.nvme_multipath configurable John Meneghini
2025-02-28 3:25 ` [PATCH 1/4] nvme-multipath: change the NVME_MULTIPATH config option John Meneghini
2025-03-05 14:33 ` Christoph Hellwig
2025-02-28 3:25 ` [PATCH 2/4] nvme-multipath: add the NVME_MULTIPATH_PARAM " John Meneghini
2025-02-28 6:28 ` Nilay Shroff
2025-02-28 13:07 ` John Meneghini
2025-03-05 14:33 ` Christoph Hellwig
2025-03-12 2:35 ` John Meneghini
2025-03-12 5:19 ` Christoph Hellwig [this message]
2025-03-13 21:46 ` John Meneghini
2025-03-17 18:00 ` Keith Busch
2025-02-28 3:25 ` [PATCH 3/4] nvme: update the multipath warning in nvme_init_ns_head John Meneghini
2025-02-28 6:28 ` Nilay Shroff
2025-02-28 13:14 ` John Meneghini
2025-03-02 17:28 ` Nilay Shroff
2025-02-28 3:25 ` [PATCH 4/4] nvme: add mulitipath warning to nvme_alloc_ns John Meneghini
2025-03-05 14:37 ` Christoph Hellwig
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=20250312051958.GA11824@lst.de \
--to=hch@lst.de \
--cc=bgurney@redhat.com \
--cc=emilne@redhat.com \
--cc=jmeneghi@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=loberman@redhat.com \
--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 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.