From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Ondrej Zary <linux@rainbow-software.org>,
Grant Coady <grant_lkml@dodo.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Odd IDE performance drop 2.4 vs 2.6?
Date: Mon, 13 Jun 2005 22:25:56 +0200 [thread overview]
Message-ID: <20050613202555.GB27774@suse.de> (raw)
In-Reply-To: <1118675343.13773.1.camel@localhost.localdomain>
On Mon, Jun 13 2005, Alan Cox wrote:
> On Llu, 2005-06-13 at 15:06, Nick Piggin wrote:
> > > Make sure you have pre-empt disabled and the antcipatory I/O scheduler
> > > disabled.
> > >
> > I don't think that those could explain it.
>
> Try it and see. The anticipatory I/O scheduler does horrible things to
> my IDE streaming performance numbers and to swap performance. It tries
> to merge I/O by delaying it which is deeply ungood when it comes to IDE
> streaming even if its good for general I/O.
Well, AS should only intentionally delay when it has competing threads
fighting for the disk. For a single threaded io case like hdparm, it
should never idle the drive. It never delays to increase merge rate, or
anything like that - only to increase spatial locality on the drive for
two or more processes accessing it simultanously.
--
Jens Axboe
next prev parent reply other threads:[~2005-06-13 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 4:03 Odd IDE performance drop 2.4 vs 2.6? Grant Coady
2005-06-13 10:43 ` Ondrej Zary
2005-06-13 13:39 ` Alan Cox
2005-06-13 14:06 ` Nick Piggin
2005-06-13 15:09 ` Alan Cox
2005-06-13 17:01 ` Ondrej Zary
2005-06-13 20:25 ` Jens Axboe [this message]
2005-06-14 2:20 ` Nick Piggin
2005-06-15 19:15 ` Ondrej Zary
2005-06-17 12:40 ` Alan Cox
2005-06-17 13:43 ` Ondrej Zary
2005-06-13 18:13 ` Grant Coady
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=20050613202555.GB27774@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=grant_lkml@dodo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=nickpiggin@yahoo.com.au \
/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