From: Steven Rostedt <rostedt@goodmis.org>
To: "Bean Huo (beanhuo)" <beanhuo@micron.com>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhad.com" <mingo@redhad.com>,
"Bart.VanAssche@sandisk.com" <Bart.VanAssche@sandisk.com>,
"rajatja@google.com" <rajatja@google.com>
Subject: Re: [RESEND PATCH v1 2/2] trace: events: block: Add tag in block trace events
Date: Mon, 16 Apr 2018 11:29:26 -0400 [thread overview]
Message-ID: <20180416112926.7b44d03f@gandalf.local.home> (raw)
In-Reply-To: <64d6073b28b140cda3e5870a54e0a7bc@SIWEX5A.sing.micron.com>
On Mon, 16 Apr 2018 14:33:29 +0000
"Bean Huo (beanhuo)" <beanhuo@micron.com> wrote:
> Print the request tag along with other information in block trace events
> when tracing request , and unplug type (Sync / Async).
>
> Signed-off-by: Bean Huo <beanhuo@micron.com>
I don't see any issue with the tracing part.
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Others need to check the content.
-- Steve
> ---
> include/trace/events/block.h | 36 +++++++++++++++++++++++++-----------
> 1 file changed, 25 insertions(+), 11 deletions(-)
>
next prev parent reply other threads:[~2018-04-16 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 14:33 [RESEND PATCH v1 2/2] trace: events: block: Add tag in block trace events Bean Huo (beanhuo)
2018-04-16 15:29 ` Steven Rostedt [this message]
2018-04-16 20:49 ` Bart Van Assche
2018-04-23 12:43 ` Steffen Maier
2018-04-23 13:34 ` Steven Rostedt
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=20180416112926.7b44d03f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=Bart.VanAssche@sandisk.com \
--cc=axboe@kernel.dk \
--cc=beanhuo@micron.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mingo@redhad.com \
--cc=rajatja@google.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