From: Jens Axboe <jaxboe@fusionio.com>
To: Tao Ma <tm@tao.ma>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blktrace: Use rq->cmd_flags directly in blk_add_trace_rq.
Date: Fri, 11 Mar 2011 20:12:37 +0100 [thread overview]
Message-ID: <4D7A7425.4030400@fusionio.com> (raw)
In-Reply-To: <1299219358-17507-1-git-send-email-tm@tao.ma>
On 2011-03-04 07:15, Tao Ma wrote:
> From: Tao Ma <boyu.mt@taobao.com>
>
> In blk_add_trace_rq, we only chose the minor 2 bits from
> request's cmd_flags and did some check for discard.
> so most of other flags(e.g, REQ_SYNC) are missing.
>
> For example, with a sync write after blkparse we get:
> 8,16 1 1 0.001776503 7509 A WS 1349632 + 1024 <- (8,17) 1347584
> 8,16 1 2 0.001776813 7509 Q WS 1349632 + 1024 [dd]
> 8,16 1 3 0.001780395 7509 G WS 1349632 + 1024 [dd]
> 8,16 1 5 0.001783186 7509 I W 1349632 + 1024 [dd]
> 8,16 1 11 0.001816987 7509 D W 1349632 + 1024 [dd]
> 8,16 0 2 0.006218192 0 C W 1349632 + 1024 [0]
>
> Since now we have integrated the flags of both bio and request,
> it is safe to pass rq->cmd_flags directly to __blk_add_trace.
>
> With this patch, after a sync write we get:
> 8,16 1 1 0.001776900 5425 A WS 1189888 + 1024 <- (8,17) 1187840
> 8,16 1 2 0.001777179 5425 Q WS 1189888 + 1024 [dd]
> 8,16 1 3 0.001780797 5425 G WS 1189888 + 1024 [dd]
> 8,16 1 5 0.001783402 5425 I WS 1189888 + 1024 [dd]
> 8,16 1 11 0.001817468 5425 D WS 1189888 + 1024 [dd]
> 8,16 0 2 0.005640709 0 C WS 1189888 + 1024 [0]
Thanks, applied!
--
Jens Axboe
prev parent reply other threads:[~2011-03-11 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 6:15 [PATCH] blktrace: Use rq->cmd_flags directly in blk_add_trace_rq Tao Ma
2011-03-09 14:06 ` Tao Ma
2011-03-09 14:31 ` Jeff Moyer
2011-03-11 19:12 ` Jens Axboe [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=4D7A7425.4030400@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tm@tao.ma \
/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