From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 3/3] nvme: deprecate the multipath=0 module option
Date: Tue, 20 Nov 2018 17:27:34 +0100 [thread overview]
Message-ID: <20181120162734.2013-4-hch@lst.de> (raw)
In-Reply-To: <20181120162734.2013-1-hch@lst.de>
This was intended as a bridge for pre-existing setups if there were
any, and is not intended to build long-term solutions on top.
Explicitly it and print a warning for each controller found when it
is set.
Signed-off-by: Christoph Hellwig <hch at lst.de>
---
drivers/nvme/host/multipath.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/nvme/host/multipath.c b/drivers/nvme/host/multipath.c
index eec44e5ec294..3851c09695b5 100644
--- a/drivers/nvme/host/multipath.c
+++ b/drivers/nvme/host/multipath.c
@@ -273,9 +273,15 @@ int nvme_mpath_alloc_disk(struct nvme_ctrl *ctrl, struct nvme_ns_head *head)
* We also do this for private namespaces as the namespace sharing data could
* change after a rescan.
*/
- if (!(ctrl->subsys->cmic & (1 << 1)) || !multipath)
+ if (!(ctrl->subsys->cmic & (1 << 1)))
return 0;
+ if (!multipath) {
+ dev_warn(ctrl->device,
+"multipath=0 module option is deprecated and will be removed in 2020.\n");
+ return 0;
+ }
+
q = blk_alloc_queue_node(GFP_KERNEL, ctrl->numa_node);
if (!q)
goto out;
--
2.19.1
next prev parent reply other threads:[~2018-11-20 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 16:27 tweak multipath kconfig and options Christoph Hellwig
2018-11-20 16:27 ` [PATCH 1/3] nvme: enable multipathing by default Christoph Hellwig
2018-11-20 18:47 ` Keith Busch
2018-11-21 8:27 ` Christoph Hellwig
2018-11-22 2:44 ` Sagi Grimberg
2018-11-26 15:40 ` Keith Busch
2018-11-20 16:27 ` [PATCH 2/3] nvme: warn when finding multi-port subsystems without multipathing enabled Christoph Hellwig
2018-11-22 2:45 ` Sagi Grimberg
2018-11-20 16:27 ` Christoph Hellwig [this message]
2018-11-22 2:49 ` [PATCH 3/3] nvme: deprecate the multipath=0 module option Sagi Grimberg
2018-11-27 15:06 ` [PATCH 3/3 v2] " 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=20181120162734.2013-4-hch@lst.de \
--to=hch@lst.de \
/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