From: Jens Axboe <jens.axboe@oracle.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [blktrace] unplug queue trace action is missed at some places
Date: Mon, 14 May 2007 07:40:46 +0000 [thread overview]
Message-ID: <20070514074046.GC7572@kernel.dk> (raw)
In-Reply-To: <1178897976.3335.20.camel@dhcp0-54.sw.ru>
On Fri, May 11 2007, Vasily Tarasov wrote:
> Hello all,
>
> The function blk_start_queueing() calls __generic_unplug_device()
> function directly without tracing BLK_TA_UNPLUG_IO action. So I have an
> odd output of blktrace, when requests go through the plugged queue. I
> suppose it's a BUG, or do I miss something?
The unplug trace is meant to log upper layers doing an unplug to start
IO, not internal use that wants to kick the queue for whatever reasons.
We could log those as well, but it would be preferential to seperate
them.
blk_start_queuing() is one such call, for instance.
--
Jens Axboe
next prev parent reply other threads:[~2007-05-14 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 15:39 [blktrace] unplug queue trace action is missed at some places Vasily Tarasov
2007-05-11 15:50 ` Vasily Tarasov
2007-05-14 7:40 ` Jens Axboe [this message]
2007-05-14 8:03 ` Vasily Tarasov
2007-05-14 8:08 ` Jens Axboe
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=20070514074046.GC7572@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-btrace@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).