From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH V2 0/2] nvme-trace: Add support for fabrics command
Date: Tue, 7 May 2019 04:46:42 +0900 [thread overview]
Message-ID: <20190506194644.11109-1-minwoo.im.dev@gmail.com> (raw)
The first one introduces a new inline function to check whether the
given nvme command is for fabrics or not. We do the checks in many
places so that we can have it as an inline.
The second patch is the actual commit to support fabrics command
tracing with updating review comments on previous V1. Actually it has
been updated entirely, but keep it tracked for the history and make this
patch V2.
I would really appreciate it if they are reviewed.
Thanks,
Changes to V1:
- fabrics commands should also be decoded, not just showing that it's
a fabrics command. (Christoph)
- do not make it within nvme admin commands (Chaitanya)
Minwoo Im (2):
nvme: Introduce nvme_is_fabrics to check fabrics cmd
nvme-trace: Add support to trace fabrics command
drivers/nvme/host/core.c | 7 +++-
drivers/nvme/host/fabrics.c | 2 +-
drivers/nvme/host/trace.c | 67 +++++++++++++++++++++++++++++++
drivers/nvme/host/trace.h | 37 +++++++++++++++++
drivers/nvme/target/core.c | 2 +-
drivers/nvme/target/fabrics-cmd.c | 2 +-
drivers/nvme/target/fc.c | 2 +-
include/linux/nvme.h | 7 +++-
8 files changed, 120 insertions(+), 6 deletions(-)
--
2.17.1
next reply other threads:[~2019-05-06 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 19:46 Minwoo Im [this message]
2019-05-06 19:46 ` [PATCH 1/2] nvme: Introduce nvme_is_fabrics to check fabrics cmd Minwoo Im
2019-05-06 22:41 ` Chaitanya Kulkarni
2019-05-06 22:59 ` Minwoo Im
2019-05-08 7:23 ` Christoph Hellwig
2019-05-06 19:46 ` [PATCH V2 2/2] nvme-trace: Add support to trace fabrics command Minwoo Im
2019-05-06 22:38 ` Chaitanya Kulkarni
2019-05-06 22:56 ` Minwoo Im
2019-05-07 1:37 ` Chaitanya Kulkarni
2019-05-07 10:43 ` Minwoo Im
2019-05-08 7:25 ` Christoph Hellwig
2019-05-08 8:26 ` 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=20190506194644.11109-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox