From: Jens Axboe <axboe@kernel.dk>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] blk: fix a wrong accounting of hd_struct->in_flight
Date: Thu, 14 Oct 2010 14:55:19 +0200 [thread overview]
Message-ID: <4CB6FDB7.5010501@kernel.dk> (raw)
In-Reply-To: <4CB6FC1C.3050801@jp.fujitsu.com>
On 2010-10-14 14:48, Yasuaki Ishimatsu wrote:
> Index: linux-2.6.36-rc7/block/blk-core.c
> ===================================================================
> --- linux-2.6.36-rc7.orig/block/blk-core.c 2010-10-07 05:39:52.000000000 +0900
> +++ linux-2.6.36-rc7/block/blk-core.c 2010-10-14 17:25:43.000000000 +0900
> @@ -66,9 +66,15 @@ static void drive_stat_acct(struct reque
> cpu = part_stat_lock();
> part = disk_map_sector_rcu(rq->rq_disk, blk_rq_pos(rq));
>
> - if (!new_io)
> + if (!new_io) {
> + if (unlikely(rq->part != part)) {
> + part_dec_in_flight(rq->part, rw);
> + part_inc_in_flight(part, rw);
> + rq->part = part;
> + }
> part_stat_inc(cpu, part, merges[rw]);
> - else {
> + } else {
> + rq->part = part;
> part_round_stats(cpu, part);
> part_inc_in_flight(part, rw);
> }
I was thinking that we'd do away with the lookup always if ->part was
already set. It will probably require a quiscing of IO on partition
table reload, though.
--
Jens Axboe
next prev parent reply other threads:[~2010-10-14 12:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 6:38 [PATCH] blk: fix a wrong accounting of hd_struct->in_flight Yasuaki Ishimatsu
2010-10-12 8:19 ` Jens Axboe
2010-10-14 12:48 ` [PATCH v2] " Yasuaki Ishimatsu
2010-10-14 12:55 ` Jens Axboe [this message]
2010-10-15 8:39 ` [PATCH v3] " Yasuaki Ishimatsu
2010-10-15 10:04 ` Jens Axboe
2010-10-18 8:28 ` [PATCH v4] " Yasuaki Ishimatsu
2010-10-18 8:34 ` Jens Axboe
2010-10-18 12:19 ` [PATCH v5] " Yasuaki Ishimatsu
2010-10-18 12:21 ` Jens Axboe
2010-10-19 2:22 ` Yasuaki Ishimatsu
2010-10-19 10:02 ` Jens Axboe
2010-10-14 6:07 ` [PATCH] " KOSAKI Motohiro
2010-10-14 12:44 ` Jens Axboe
2010-10-14 23:30 ` Paul E. McKenney
2010-10-15 7:30 ` 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=4CB6FDB7.5010501@kernel.dk \
--to=axboe@kernel.dk \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox