From: Jens Axboe <axboe@kernel.dk>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Namhyung Kim <namhyung@gmail.com>,
Shaohua Li <shaohua.li@intel.com>,
linux-kernel@vger.kernel.org, Divyesh Shah <dpshah@google.com>
Subject: Re: [PATCH] block: call elv_bio_merged() when merged
Date: Fri, 20 May 2011 21:21:03 +0200 [thread overview]
Message-ID: <4DD6BF1F.7010403@kernel.dk> (raw)
In-Reply-To: <20110520191907.GA6379@redhat.com>
On 2011-05-20 21:19, Vivek Goyal wrote:
> On Fri, May 20, 2011 at 08:50:47PM +0200, Jens Axboe wrote:
>> On 2011-05-20 11:51, Namhyung Kim wrote:
>>> Hello,
>>>
>>> 2011-05-20 (금), 16:31 +0800, Shaohua Li:
>>>> 2011/5/20 Namhyung Kim <namhyung@gmail.com>:
>>>>> Commit 73c101011926 ("block: initial patch for on-stack per-task plugging")
>>>>> removed calls to elv_bio_merged() when @bio merged with @req. Re-add them.
>>>>>
>>>>> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
>>>>> Cc: Divyesh Shah <dpshah@google.com>
>>>>> ---
>>>>> block/blk-core.c | 2 ++
>>>>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>>>>
>>>>> diff --git a/block/blk-core.c b/block/blk-core.c
>>>>> index 3fe00a14822a..4dc02ef5fc82 100644
>>>>> --- a/block/blk-core.c
>>>>> +++ b/block/blk-core.c
>>>>> @@ -1132,6 +1132,7 @@ static bool bio_attempt_back_merge(struct request_queue *q, struct request *req,
>>>>> req->ioprio = ioprio_best(req->ioprio, bio_prio(bio));
>>>>>
>>>>> drive_stat_acct(req, 0);
>>>>> + elv_bio_merged(q, req, bio);
>>>>> return true;
>>>>> }
>>>>>
>>>>> @@ -1173,6 +1174,7 @@ static bool bio_attempt_front_merge(struct request_queue *q,
>>>>> req->ioprio = ioprio_best(req->ioprio, bio_prio(bio));
>>>>>
>>>>> drive_stat_acct(req, 0);
>>>>> + elv_bio_merged(q, req, bio);
>>>>> return true;
>>>>> }
>>>> Looks you should do this in __make_request. when the routine is called
>>>> in attempt_plug_merge, the request isn't added to elevator yet.
>>>>
>>>
>>> Hmm.. anyway it is merged. Is there any reason why we shouldn't collect
>>> the stat - or invoke the callback routine - if the @req is not in the
>>> elevator? Or we need to add a separate stat item for this case?
>>
>> Your patch should be safe, it's essentially only for the cgroup stuff
>> that does its own accounting and has appropriate protection for it. We'd
>> want to do this for both the plug and not-plugged merge case.
>>
>> It's a bit of a shame to add this though, since now we are hitting the
>> cgroup lock for each merge.
>
> I think wer can make MERGED per cpu as I have done in my other patch
> series for following dispatch stats.
>
> BLKIO_STAT_CPU_SECTORS,
> /* Total bytes transferred */
> BLKIO_STAT_CPU_SERVICE_BYTES,
> /* Total IOs serviced, post merge */
> BLKIO_STAT_CPU_SERVICED,
Yep, lets please do that and we can re-instate the merge calls with
that, too.
> Jens are you planning to merge lockless throttling series? Once that gets
> merged, we can convert this MERGED stat also per cpu and get rid of need of
> taking blkg->stats_lock.
Merged them about an hour ago :-)
Send further updates relative to for-2.6.40/core.
--
Jens Axboe
next prev parent reply other threads:[~2011-05-20 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 5:28 Namhyung Kim
2011-05-20 8:31 ` Shaohua Li
2011-05-20 9:51 ` Namhyung Kim
2011-05-20 18:50 ` Jens Axboe
2011-05-20 19:19 ` Vivek Goyal
2011-05-20 19:21 ` Jens Axboe [this message]
2011-05-20 21:02 ` Vivek Goyal
2011-05-23 2:10 ` Shaohua Li
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=4DD6BF1F.7010403@kernel.dk \
--to=axboe@kernel.dk \
--cc=dpshah@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=shaohua.li@intel.com \
--cc=vgoyal@redhat.com \
/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
Powered by JetHome