From: Jens Axboe <axboe@suse.de>
To: Peter Osterlund <petero2@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.2-pre3] Harddisk Performance
Date: Sat, 5 Jan 2002 12:33:46 +0100 [thread overview]
Message-ID: <20020105123346.X8673@suse.de> (raw)
In-Reply-To: <20011229162930.GA317@elfie.cavy.de> <20011229181717.C1821@suse.de> <m2sn9m5bcv.fsf@pengo.localdomain>
In-Reply-To: <m2sn9m5bcv.fsf@pengo.localdomain>
On Fri, Jan 04 2002, Peter Osterlund wrote:
> Jens Axboe <axboe@suse.de> writes:
>
> > On Sat, Dec 29 2001, Heinz Diehl wrote:
> > >
> > > Running 2.5.2-pre3, hdparm shows up very poor harddisk performance
> > > on my system compared to 2.4.x:
> >
> > Yes I just noticed that too (someone else reported it) -- seems to be
> > due to missed merges, I'm investigating.
>
> I have found that if the elevator says BACK_MERGE or FRONT_MERGE, but
> the request queue doesn't allow the merge, the request will be put
> last in the queue instead of next to the request where the merge would
> have been done if allowed.
Excellent spotting! Applied.
--
Jens Axboe
prev parent reply other threads:[~2002-01-05 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-29 16:29 [2.5.2-pre3] Harddisk Performance Heinz Diehl
2001-12-29 17:17 ` Jens Axboe
2002-01-04 16:28 ` Peter Osterlund
2002-01-05 11:33 ` Jens Axboe [this message]
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=20020105123346.X8673@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.