[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20241121220235.40576-1-bgurney@redhat.com>
Date: Thu, 21 Nov 2024 17:02:35 -0500
From: Bryan Gurney <bgurney@...hat.com>
To: linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org,
kbusch@...nel.org,
hch@....de,
sagi@...mberg.me,
axboe@...nel.dk,
mpe@...erman.id.au,
naveen@...nel.org,
maddy@...ux.ibm.com,
kernel@...0n.name
Cc: jmeneghi@...hat.com,
bmarzins@...hat.com,
Bryan Gurney <bgurney@...hat.com>
Subject: [PATCH 0/1] nvme: remove CONFIG_NVME_MULTIPATH
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
Powered by blists - more mailing lists