From: Jens Axboe <jens.axboe@oracle.com>
To: "Alan D. Brunelle" <Alan.Brunelle@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH linux-2.6-block.git] Fix blktrace trace ordering for plug branch
Date: Mon, 30 Apr 2007 08:46:16 +0200 [thread overview]
Message-ID: <20070430064615.GB21015@kernel.dk> (raw)
In-Reply-To: <46325A6F.4050705@pobox.com>
On Fri, Apr 27 2007, Alan D. Brunelle wrote:
> The attached patch will correct the ordering of trace output between
> request queue insertions (I) and unplug calls (U). Right now the insert
> precedes the unplug, which just isn't right:
>
> 65,128 0 1 67.699868965 7882 Q R 0 + 1 [aiod]
> 65,128 0 2 67.699876462 7882 G R 0 + 1 [aiod]
> 65,128 0 3 67.699878286 7882 P W [aiod]
> 65,128 0 4 67.699880491 7882 I R 0 + 1 [aiod]
> 65,128 0 5 67.699887589 7882 U R [aiod] 1
> 65,128 0 6 67.699898317 54 D R 0 + 1 [kblockd/0]
> 65,128 2 153 67.700126590 0 C R 0 + 1 [0]
>
> With the patch provided the unplug comes first:
>
> 65,128 3 1 0.000000000 7045 Q R 0 + 1 [aiod]
> 65,128 3 2 0.000002295 7045 G R 0 + 1 [aiod]
> 65,128 3 3 0.000002617 7045 P W [aiod]
> 65,128 3 4 0.000003685 7045 U R [aiod] 1
> 65,128 3 5 0.000004107 7045 I R 0 + 1 [aiod]
> 65,128 3 6 0.000009491 57 D R 0 + 1 [kblockd/3]
> 65,128 2 1 0.000232447 0 C R 0 + 1 [0]
>
> Jens: If you agree, the patch can be applied to your plug branch for
> git://git.kernel.dk/data/git/linux-2.6-block.git
Thanks, with that applied the unplug ordering should be the same after
the plugging changes. Applied.
--
Jens Axboe
prev parent reply other threads:[~2007-04-30 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 20:17 [PATCH linux-2.6-block.git] Fix blktrace trace ordering for plug branch Alan D. Brunelle
2007-04-30 6:46 ` 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=20070430064615.GB21015@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Alan.Brunelle@pobox.com \
--cc=linux-kernel@vger.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 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.