From: Andrew Morton <akpm@osdl.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: performance regression from block merge
Date: Thu, 21 Dec 2006 12:14:30 -0800 [thread overview]
Message-ID: <20061221121430.33392935.akpm@osdl.org> (raw)
In-Reply-To: <20061221194741.GH17199@kernel.dk>
On Thu, 21 Dec 2006 20:47:41 +0100
Jens Axboe <jens.axboe@oracle.com> wrote:
> On Thu, Dec 21 2006, Jens Axboe wrote:
> > On Thu, Dec 21 2006, Andrew Morton wrote:
> > >
> > > Jens, elapsed time for `mke2fs /dev/hdc5' with the anticipatory scheduler
> > > (at least) has gone from nine seconds to sixty as a result of the recent
> > > block merge.
> >
> > About when? I'll double check and test here, I'm assuming you mean since
> > 2.6.19?
In yesterday's merge. I double-checked by testing yesterday's-Linus versus
yesterday's-Linus-plus-yesterday's-git-block. The latter was slow.
> Auch, brown paper bag time, I spotted an obvious typo in the recent
> merge. Does this fix it? It should be safe to kill the ->special check,
> but lets leave that for another time.
>
> diff --git a/block/elevator.c b/block/elevator.c
> index 62c7a30..536be74 100644
> --- a/block/elevator.c
> +++ b/block/elevator.c
> @@ -82,7 +82,7 @@ inline int elv_rq_merge_ok(struct reques
> /*
> * must be same device and not a special request
> */
> - if (rq->rq_disk != bio->bi_bdev->bd_disk || !rq->special)
> + if (rq->rq_disk != bio->bi_bdev->bd_disk || rq->special)
> return 0;
>
> if (!elv_iosched_allow_merge(rq, bio))
>
I shan't be near that machine for eight hours or so; shall test then.
next prev parent reply other threads:[~2006-12-21 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 19:25 Andrew Morton
2006-12-21 19:35 ` Jens Axboe
2006-12-21 19:47 ` Jens Axboe
2006-12-21 20:14 ` Andrew Morton [this message]
2006-12-21 20:18 ` 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=20061221121430.33392935.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®