From: Minwoo Im <minwoo.im.dev@gmail.com>
To: linux-nvme@lists.infradead.org
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Minwoo Im <minwoo.im.dev@gmail.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Subject: [nvme-cli PATCH] nvme: add [--mpath|-M] option to io-passthru
Date: Sun, 14 Feb 2021 20:01:26 +0900 [thread overview]
Message-ID: <20210214110126.24023-3-minwoo.im.dev@gmail.com> (raw)
In-Reply-To: <20210214110126.24023-1-minwoo.im.dev@gmail.com>
`io-passthru` command is to submit a I/O command to controller with a
namespace specified. Kernel driver does not allow userspace to I/O
passthrough in case that controller has multiple namespaces attached.
NVME_IOCTL_IO_CMD will return -EINVAL error from the kernel driver.
This patch added an option `--mpath|-M` option to the `io-passthru`
command to support specifying device namespace id to I/O. This option
will make `--namespace-id` option to be used to find out the namespae
instance to the kernel side even it's a hidden blkdev (e.g.,
/dev/nvmeXcYnZ).
This feature can be used to debug or test the broken path for ANA case
by specifying the target namespace of a controller to I/O.
nvme io-passthru /dev/nvme0 --namespace-id=123 --opcode=0x2 --data-len=512 --read --mpath
Signed-off-by: Minwoo Im <minwoo.im.dev@gmail.com>
---
linux/nvme_ioctl.h | 1 +
nvme.c | 20 ++++++++++++++++++++
2 files changed, 21 insertions(+)
diff --git a/linux/nvme_ioctl.h b/linux/nvme_ioctl.h
index d569414211d1..578faaee62b6 100644
--- a/linux/nvme_ioctl.h
+++ b/linux/nvme_ioctl.h
@@ -87,5 +87,6 @@ struct nvme_passthru_cmd64 {
#define NVME_IOCTL_RESCAN _IO('N', 0x46)
#define NVME_IOCTL_ADMIN64_CMD _IOWR('N', 0x47, struct nvme_passthru_cmd64)
#define NVME_IOCTL_IO64_CMD _IOWR('N', 0x48, struct nvme_passthru_cmd64)
+#define NVME_IOCTL_MPATH_IO _IOWR('N', 0x49, struct nvme_passthru_cmd)
#endif /* _UAPI_LINUX_NVME_IOCTL_H */
diff --git a/nvme.c b/nvme.c
index c79edbda17ed..9dea66edcabe 100644
--- a/nvme.c
+++ b/nvme.c
@@ -5109,6 +5109,7 @@ static int passthru(int argc, char **argv, int ioctl_cmd, const char *desc, stru
int read;
int write;
__u8 prefill;
+ bool mpath;
};
struct config cfg = {
@@ -5129,6 +5130,7 @@ static int passthru(int argc, char **argv, int ioctl_cmd, const char *desc, stru
.cdw15 = 0,
.input_file = "",
.prefill = 0,
+ .mpath = false,
};
const char *opcode = "opcode (required)";
@@ -5153,6 +5155,7 @@ static int passthru(int argc, char **argv, int ioctl_cmd, const char *desc, stru
const char *re = "set dataflow direction to receive";
const char *wr = "set dataflow direction to send";
const char *prefill = "prefill buffers with known byte-value, default 0";
+ const char *mpath = "multipath I/O (valid only if io-passthru)";
OPT_ARGS(opts) = {
OPT_BYTE("opcode", 'o', &cfg.opcode, opcode),
@@ -5177,6 +5180,7 @@ static int passthru(int argc, char **argv, int ioctl_cmd, const char *desc, stru
OPT_FLAG("dry-run", 'd', &cfg.dry_run, dry),
OPT_FLAG("read", 'r', &cfg.read, re),
OPT_FLAG("write", 'w', &cfg.write, wr),
+ OPT_FLAG("mpath", 'M', &cfg.mpath, mpath),
OPT_END()
};
@@ -5184,6 +5188,22 @@ static int passthru(int argc, char **argv, int ioctl_cmd, const char *desc, stru
if (fd < 0)
goto ret;
+ if (cfg.mpath) {
+ if (!cfg.namespace_id) {
+ fprintf(stderr, "mpath should be with --namespace-id\n");
+ err = -EINVAL;
+ goto close_fd;
+ }
+
+ if (!is_chardev()) {
+ fprintf(stderr, "mpath should be with chardev (e.g., /dev/nvme0)\n");
+ err = -EINVAL;
+ goto close_fd;
+ }
+
+ ioctl_cmd = NVME_IOCTL_MPATH_IO;
+ }
+
if (strlen(cfg.input_file)){
wfd = open(cfg.input_file, O_RDONLY,
S_IRUSR | S_IRGRP | S_IROTH);
--
2.17.1
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2021-02-14 11:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 11:01 [PATCH 0/2] nvme: support I/O passthrough for multipath Minwoo Im
2021-02-14 11:01 ` [PATCH] nvme: introduce passthrough ioctl " Minwoo Im
2021-02-15 17:02 ` Keith Busch
2021-02-16 9:51 ` Minwoo Im
2021-02-16 17:57 ` Keith Busch
2021-02-17 2:14 ` Minwoo Im
2021-02-18 8:40 ` Christoph Hellwig
2021-02-18 8:48 ` Javier González
2021-02-19 21:27 ` Minwoo Im
2021-02-19 21:26 ` Minwoo Im
2021-02-14 11:01 ` Minwoo Im [this message]
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=20210214110126.24023-3-minwoo.im.dev@gmail.com \
--to=minwoo.im.dev@gmail.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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