From: Andrea Arcangeli <andrea@suse.de>
To: Neil Schemenauer <nas@arctrix.com>
Cc: linux-kernel@vger.kernel.org, axboe@suse.de, akpm@digeo.com,
conman@kolivas.net
Subject: Re: [PATCH][CFT] new IO scheduler for 2.4.20
Date: Mon, 21 Apr 2003 13:33:46 +0200 [thread overview]
Message-ID: <20030421113346.GE21877@dualathlon.random> (raw)
In-Reply-To: <20030417172818.GA8848@glacier.arctrix.com>
On Thu, Apr 17, 2003 at 10:28:19AM -0700, Neil Schemenauer wrote:
> Hi all,
>
> Recently I was bitten badly by bad IO scheduler behavior on an important
> Linux server. An easy way to trigger this problem is to start a
> streaming write process:
>
> while :
> do
> dd if=/dev/zero of=foo bs=1M count=512 conv=notrunc
> done
>
> and then try doing a bunch of small reads:
>
> time (find kernel-tree -type f | xargs cat > /dev/null)
can you try the above on 2.4.21pre5aa2? I also spent effort to fix it
some month ago.
The interesting patch is this:
http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.21pre5aa2/9981_elevator-lowlatency-4
the reason 2.4 mainline stalls so much is that the size of the queue is
overkill for no good reason, so no matter the elvtune numbers, you're
going to wait several dozen mbytes to be read or written before you can
read or write the next 1k from another task.
the above patch is fairly old and it basically fixes the showstopper
problem for me, contest looks fine now and throughput still is the best.
I don't like special "read hacks" for generic kernels that are critical
with O_SYNC and journaling responsiveness too.
So I recommend to apply the above 2.4 patch if you suffer any I/O
latency issue.
Andrea
next prev parent reply other threads:[~2003-04-21 11:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 17:28 Neil Schemenauer
2003-04-17 20:41 ` Andrew Morton
2003-04-20 18:26 ` Neil Schemenauer
2003-04-20 22:06 ` Marc-Christian Petersen
2003-04-21 1:46 ` Neil Schemenauer
2003-04-21 11:33 ` Andrea Arcangeli [this message]
2003-05-30 22:09 Neil Schemenauer
2003-05-30 23:40 ` Con Kolivas
2003-05-31 0:52 ` Neil Schemenauer
2003-05-30 17:58 ` Robert Love
2003-06-02 17:21 Andreas Dilger
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=20030421113346.GE21877@dualathlon.random \
--to=andrea@suse.de \
--cc=akpm@digeo.com \
--cc=axboe@suse.de \
--cc=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nas@arctrix.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
all inboxes | Powered by JetHome®