public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jianpeng Ma" <majianpeng@gmail.com>
To: axboe <axboe@kernel.dk>
Cc: tj <tj@kernel.org>, rostedt <rostedt@goodmis.org>,
	fweisbec <fweisbec@gmail.com>, mingo <mingo@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Li Zefan" <lizf@cn.fujitsu.com>, "Tao Ma" <boyu.mt@taobao.com>
Subject: Re: Re: Why blktrace didn't trace requests merge?
Date: Tue, 18 Sep 2012 14:33:32 +0800	[thread overview]
Message-ID: <201209181433295154570@gmail.com> (raw)
In-Reply-To: 50580B51.70300@kernel.dk

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 2508 bytes --]

On 2012-09-18 13:49 Jens Axboe <axboe@kernel.dk> Wrote:
>On 2012-09-18 02:30, Jianpeng Ma wrote:
>> On 2012-09-18 02:27 Jens Axboe <axboe@kernel.dk> Wrote:
>>> On 2012-09-17 19:55, Tejun Heo wrote:
>>>> (cc'ing Jens)
>>>>
>>>> On Mon, Sep 17, 2012 at 09:22:28AM -0400, Steven Rostedt wrote:
>>>>> On Mon, 2012-09-17 at 19:33 +0800, Jianpeng Ma wrote:
>>>>>> Hi all:
>>>>>> 	I used blktrace to trace some io.But i can't find requests merge. I searched the code and did't not find.
>>>>>> 	Why? 
>>>>>> 									
>>>>>
>>>>> No idea. I don't use blktrace much, but I Cc'd those that understand it
>>>>> better than I.
>>>
>>> Works for me:
>>>
>>> [...]
>>>
>>>
>>>  8,0    0       26     0.009147735   664  A  WS 315226143 + 8 <- (8,7) 19406344
>>>  8,0    0       27     0.009148677   664  Q  WS 315226143 + 8 [btrfs-submit-1]
>>>  8,0    0       28     0.009152967   664  G  WS 315226143 + 8 [btrfs-submit-1]
>>>  8,0    0       29     0.009154242   664  P   N [btrfs-submit-1]
>>>  8,0    0       30     0.009155538   664  A  WS 315226151 + 8 <- (8,7) 19406352
>>>  8,0    0       31     0.009155743   664  Q  WS 315226151 + 8 [btrfs-submit-1]
>>>  8,0    0       32     0.009157086   664  M  WS 315226151 + 8 [btrfs-submit-1]
>>>  8,0    0       33     0.009158716   664  I  WS 315226143 + 16 [btrfs-submit-1]
>>>
>>> That's from a quick trace of /dev/sda. I started blktrace, then did:
>>>
>>> $ dd if=/dev/zero of=foo bs=4k count=128 && sync
>>>
>>> to ensure that I knew merges would be happening. Output stats at the end:
>>>
>>> Total (sda):
>>> Reads Queued:           7,       44KiB  Writes Queued:         447,     7692KiB
>>> Read Dispatches:        7,       44KiB  Write Dispatches:      416,     7692KiB
>>> Reads Requeued:         0               Writes Requeued:         0
>>> Reads Completed:        7,       44KiB  Writes Completed:      435,     5864KiB
>>> Read Merges:            0,        0KiB  Write Merges:           23,      428KiB
>>> IO unplugs:            78               Timer unplugs:           0
>>>
>>> -- 
>>> Jens Axboe
>>>
>> First, Thanks your time!
>> If i understand correctly, the merge of your example is bio with
>> request, not request wiht request.  Yes or no?
>
>It is bio to request, correct. Request to request merges are relatively
>more rare.
>
>-- 
>Jens Axboe
>
Thanks very much, I know.

Jianpengÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

      reply	other threads:[~2012-09-18  6:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 11:33 Why blktrace didn't trace requests merge? Jianpeng Ma
2012-09-17 13:22 ` Steven Rostedt
2012-09-17 17:55   ` Tejun Heo
2012-09-17 18:03     ` KOSAKI Motohiro
2012-09-17 18:27     ` Jens Axboe
2012-09-18  0:30       ` Jianpeng Ma
2012-09-18  5:49         ` Jens Axboe
2012-09-18  6:33           ` Jianpeng Ma [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=201209181433295154570@gmail.com \
    --to=majianpeng@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=boyu.mt@taobao.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tj@kernel.org \
    /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