linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung.kim@lge.com>
To: Tejun Heo <tj@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] block: introduce BIO_IN_FLIGHT flag
Date: Mon, 09 Jan 2012 11:57:43 +0900	[thread overview]
Message-ID: <4F0A57A7.4070508@lge.com> (raw)
In-Reply-To: <20120109015628.GB16360@mtj.dyndns.org>

2012-01-09 10:56 AM, Tejun Heo wrote:
> On Tue, Dec 27, 2011 at 11:28:32PM +0900, Namhyung Kim wrote:
>> BIO_IN_FLIGHT flag is used for tracing block I/O completion.
>> This patch fixes tracing bio-based devices - except DM which
>> inserts completion tracepoint explicitly - that could not be
>> traced such event using blktrace.
>>
>> It won't affect tracing normal (request-based) disk devices
>> and nested bio handling paths.
>>
>> Signed-off-by: Namhyung Kim<namhyung@gmail.com>
>> ---
>>   block/blk-core.c          |    5 +++++
>>   fs/bio.c                  |    7 +++++++
>>   include/linux/blk_types.h |    1 +
>>   3 files changed, 13 insertions(+), 0 deletions(-)
>>
>> diff --git a/block/blk-core.c b/block/blk-core.c
>> index 1b4fd93af2c0..f61310323954 100644
>> --- a/block/blk-core.c
>> +++ b/block/blk-core.c
>> @@ -165,6 +165,9 @@ static void req_bio_endio(struct request *rq, struct bio *bio,
>>   	if (unlikely(rq->cmd_flags&  REQ_QUIET))
>>   		set_bit(BIO_QUIET,&bio->bi_flags);
>>
>> +	/* completion event was already reported in blk_update_request */
>> +	clear_bit(BIO_IN_FLIGHT,&bio->bi_flags);
>> +
>>   	bio->bi_size -= nbytes;
>>   	bio->bi_sector += (nbytes>>  9);
>>
>> @@ -1662,6 +1665,8 @@ void generic_make_request(struct bio *bio)
> p>   	do {
>>   		struct request_queue *q = bdev_get_queue(bio->bi_bdev);
>>
>> +		set_bit(BIO_IN_FLIGHT,&bio->bi_flags);
>> +
>>   		q->make_request_fn(q, bio);
>>
>>   		bio = bio_list_pop(current->bio_list);
>> diff --git a/fs/bio.c b/fs/bio.c
>> index b1fe82cf88cf..10fb7a1d74ba 100644
>> --- a/fs/bio.c
>> +++ b/fs/bio.c
>> @@ -1447,6 +1447,13 @@ void bio_endio(struct bio *bio, int error)
>>   	else if (!test_bit(BIO_UPTODATE,&bio->bi_flags))
>>   		error = -EIO;
>>
>> +	if (test_bit(BIO_IN_FLIGHT,&bio->bi_flags)) {
>> +		struct request_queue *q = bdev_get_queue(bio->bi_bdev);
>> +
>> +		trace_block_bio_complete(q, bio, error);
>> +		clear_bit(BIO_IN_FLIGHT,&bio->bi_flags);
>> +	}
>
> This really should be filtered from the consumer side.  Not on TP
> itself.  Doing it like this makes the TP useless for other consumers
> and adds unnecessary flag and operations on it even when the TP is not
> in use.  Why not just trigger the TP on boi_endio() and let blktrace
> probe filter out bounced or cloned completions?

I understand your concerns. However, the blktrace cannot get 
bio->bi_flags info in its current form AFAIK. Doing it will require 
extending struct blk_io_trace and it'll cause a compatibility issue,
I guess.

Anyway I think the needs of tracing bio based drivers are growing so 
it'd be great the blktrace supports it as well. Also as we've run out of 
act_mask bits, it might be needed a room for extending.

But before proceeding, I'd like to listen comments/advices from people. 
Jens?

Thanks,
Namhyung Kim

  reply	other threads:[~2012-01-09  2:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-27 14:28 [PATCH -block/for-next 0/2] blktrace: bio-based device tracing improvement v3 Namhyung Kim
2011-12-27 14:28 ` [PATCH 1/2] block: introduce BIO_IN_FLIGHT flag Namhyung Kim
2012-01-09  1:56   ` Tejun Heo
2012-01-09  2:57     ` Namhyung Kim [this message]
2012-01-09 16:41       ` Tejun Heo
2012-01-10  5:06         ` Namhyung Kim
2012-01-10 16:26           ` Tejun Heo
2011-12-27 14:28 ` [PATCH 2/2] block: don't export block_bio_complete tracepoint Namhyung Kim

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=4F0A57A7.4070508@lge.com \
    --to=namhyung.kim@lge.com \
    --cc=axboe@kernel.dk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).