From: Bryan Gurney <bgurney@redhat.com>
To: 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
Cc: jmeneghi@redhat.com, bmarzins@redhat.com,
Bryan Gurney <bgurney@redhat.com>
Subject: [PATCH 0/1] nvme: remove CONFIG_NVME_MULTIPATH
Date: Thu, 21 Nov 2024 17:02:35 -0500 [thread overview]
Message-ID: <20241121220235.40576-1-bgurney@redhat.com> (raw)
Device-mapper multipath will no longer be operating on NVMe devices,
so the nvme.core.multipath module parameter can be removed. This
series also removes the CONFIG_NVME_MULTIPATH kconfig option.
This was tested on the nvme-6.13 branch (currently showing version
6.12-rc4), with particular attention to tests nvme/033-036, and
nvme/039. These tests still passed after the removal of the
CONFIG_NVME_MULTIPATH parameter (the tests use an "rc" function,
_require_test_dev_is_not_nvme_multipath, that checks for
"nvme-subsystem" in $TEST_DEV_SYSFS, so they do not check for the
existence of CONFIG_NVME_MULTIPATH).
The blktests test nvme/005 checks for the module parameter value of
"nvme_core multipath", but this test gets skipped after this patch.
Bryan Gurney (1):
nvme: always enable multipath
arch/loongarch/configs/loongson3_defconfig | 1 -
arch/powerpc/configs/skiroot_defconfig | 1 -
drivers/nvme/host/Kconfig | 9 --
drivers/nvme/host/Makefile | 3 +-
drivers/nvme/host/core.c | 17 +---
drivers/nvme/host/ioctl.c | 3 +-
drivers/nvme/host/multipath.c | 10 +--
drivers/nvme/host/nvme.h | 97 +---------------------
drivers/nvme/host/sysfs.c | 6 --
9 files changed, 7 insertions(+), 140 deletions(-)
--
2.45.2
reply other threads:[~2024-11-21 22:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20241121220235.40576-1-bgurney@redhat.com \
--to=bgurney@redhat.com \
--cc=axboe@kernel.dk \
--cc=bmarzins@redhat.com \
--cc=hch@lst.de \
--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
all inboxes | Powered by JetHome®