From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH 0/4] nvme: update way to get qid in trace
Date: Sun, 28 Jul 2019 03:41:51 +0900 [thread overview]
Message-ID: <20190727184155.18014-1-minwoo.im.dev@gmail.com> (raw)
Hi All,
This series is mainly to support trace for lightnvm commands. To make
it support:
The first patch just simplify the exactly same operations in short by
have queue_num directly. The second one modified the condition of how
to figure out whether the given request is for admin queue or not.
In case of lightnvm, req->rq_disk might be NULL even it's a NVM command
so that we can compare the admin request queue itself.
The third one added lightnvm admin commands to nvme.h from the lightnvm
core module to support for trace of opcode names. The fourth one added
NVM I/O commands for the lightnvm for the trace.
Minwoo Im (4):
nvme: simplify nvme_req_qid()
nvme: check admin queue with ctrl->admin_q, not rq_disk
nvme: lightnvm: trace opcode name
nvme: lightnvm: trace opcode name of I/O commands for 2.0
drivers/nvme/host/lightnvm.c | 6 ------
drivers/nvme/host/nvme.h | 16 +++++++++-------
include/linux/nvme.h | 22 ++++++++++++++++++++--
3 files changed, 29 insertions(+), 15 deletions(-)
--
2.17.1
next 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 Minwoo Im [this message]
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 ` [PATCH 4/4] nvme: lightnvm: trace opcode name of I/O commands for 2.0 Minwoo Im
2019-07-27 19:47 ` 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-1-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.