From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH 4/4] nvme: lightnvm: trace opcode name of I/O commands for 2.0
Date: Sun, 28 Jul 2019 03:41:55 +0900 [thread overview]
Message-ID: <20190727184155.18014-5-minwoo.im.dev@gmail.com> (raw)
In-Reply-To: <20190727184155.18014-1-minwoo.im.dev@gmail.com>
This patch adds opcode values which are defined in OCSSD 2.0 spec. This
will make it printed a name of opcode rather than the raw value.
Cc: Keith Busch <kbusch at kernel.org>
Cc: Jens Axboe <axboe at fb.com>
Cc: Christoph Hellwig <hch at lst.de>
Cc: Sagi Grimberg <sagi at grimberg.me>
Cc: Matias Bj?rling <mb at lightnvm.io>
Cc: Javier Gonz?lez <javier at javigon.com>
Signed-off-by: Minwoo Im <minwoo.im.dev at gmail.com>
---
include/linux/nvme.h | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/include/linux/nvme.h b/include/linux/nvme.h
index fddf4c776788..d1db459dbfc1 100644
--- a/include/linux/nvme.h
+++ b/include/linux/nvme.h
@@ -566,6 +566,12 @@ enum nvme_opcode {
nvme_cmd_resv_report = 0x0e,
nvme_cmd_resv_acquire = 0x11,
nvme_cmd_resv_release = 0x15,
+
+ /* OCSSD 2.0 */
+ nvme_nvm_cmd_vec_chunk_reset = 0x90,
+ nvme_nvm_cmd_vec_chunk_write = 0x91,
+ nvme_nvm_cmd_vec_chunk_read = 0x92,
+ nvme_nvm_cmd_vec_chunk_copy = 0x93,
};
#define nvme_opcode_name(opcode) { opcode, #opcode }
@@ -581,7 +587,11 @@ enum nvme_opcode {
nvme_opcode_name(nvme_cmd_resv_register), \
nvme_opcode_name(nvme_cmd_resv_report), \
nvme_opcode_name(nvme_cmd_resv_acquire), \
- nvme_opcode_name(nvme_cmd_resv_release))
+ nvme_opcode_name(nvme_cmd_resv_release), \
+ nvme_opcode_name(nvme_nvm_cmd_vec_chunk_reset), \
+ nvme_opcode_name(nvme_nvm_cmd_vec_chunk_write), \
+ nvme_opcode_name(nvme_nvm_cmd_vec_chunk_read), \
+ nvme_opcode_name(nvme_nvm_cmd_vec_chunk_copy))
/*
--
2.17.1
next prev parent reply other threads:[~2019-07-27 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 18:41 [PATCH 0/4] nvme: update way to get qid in trace Minwoo Im
2019-07-27 18:41 ` [PATCH 1/4] nvme: simplify nvme_req_qid() Minwoo Im
2019-07-27 18:41 ` [PATCH 2/4] nvme: check admin queue with ctrl->admin_q, not rq_disk Minwoo Im
2019-07-27 18:41 ` [PATCH 3/4] nvme: lightnvm: trace opcode name Minwoo Im
2019-07-27 19:36 ` Matias Bjørling
2019-07-28 3:12 ` Minwoo Im
2019-07-27 18:41 ` Minwoo Im [this message]
2019-07-27 19:47 ` [PATCH 4/4] nvme: lightnvm: trace opcode name of I/O commands for 2.0 Matias Bjørling
2019-07-28 3:15 ` Minwoo Im
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=20190727184155.18014-5-minwoo.im.dev@gmail.com \
--to=minwoo.im.dev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.