From: Guixin Liu <kanie@linux.alibaba.com>
To: John Meneghini <jmeneghi@redhat.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Ewan Milne <emilne@redhat.com>, Bryan Gurney <bgurney@redhat.com>,
Chris Leech <cleech@redhat.com>,
Maurizio Lombardi <mlombard@redhat.com>
Subject: Re: CONFIG_NVME_MULTIPATH - Do we need this?
Date: Fri, 15 Nov 2024 09:40:47 +0800 [thread overview]
Message-ID: <72a94818-cbca-4c0d-a37d-59fba15e4dbc@linux.alibaba.com> (raw)
In-Reply-To: <889e1d2a-1cda-4979-8279-f2f665350376@redhat.com>
在 2024/11/13 08:23, John Meneghini 写道:
> Now that RHEL-10 beta has shipped we no longer support anything but
> native nvme multi-pathing and I'd like to do something about the
> multipath module parameter:
>
> bool multipath = true;
> module_param(multipath, bool, 0444);
> MODULE_PARM_DESC(multipath,
> "turn on native support for multiple controllers per subsystem");
>
> I'd like to remove this parameter from nvme_core/multipath.c. The fact
> is, setting nvme_core.multipath=N never worked in anything but RHEL
> and keeping it around only causes confusion.
>
> For that matter, I'd like to remove the CONFIG_NVME_MULTIPATH kconfig
> option altogether.
>
> Does anybody actually use this?
>
> # CONFIG_NVME_MULTIPATH is not set
>
> Do we actually support running nvme without multipath.c ?
>
If the user want use dm-multipath instead of nvme-multipath, but the
kernel's CONFIG_NVME_MULTIPATH is y, they can set this parameter to
disable nvme-multipath.
Best Regards,
Guixin Liu
next prev parent reply other threads:[~2024-11-15 1:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 0:23 CONFIG_NVME_MULTIPATH - Do we need this? John Meneghini
2024-11-14 16:47 ` Christoph Hellwig
2024-11-15 1:40 ` Guixin Liu [this message]
2024-11-18 7:03 ` Christoph Hellwig
2024-11-18 15:31 ` Keith Busch
2024-11-19 10:18 ` Nilay Shroff
2024-11-19 14:55 ` John Meneghini
2024-11-20 10:49 ` Nilay Shroff
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=72a94818-cbca-4c0d-a37d-59fba15e4dbc@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=bgurney@redhat.com \
--cc=cleech@redhat.com \
--cc=emilne@redhat.com \
--cc=jmeneghi@redhat.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@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