From: "Antonio Larrosa Jiménez" <antlarr@tedial.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Doug Ledford <dledford@redhat.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: iowait problems on 2.6, not on 2.4
Date: Mon, 31 May 2004 13:24:37 +0200 [thread overview]
Message-ID: <200405311324.38424.antlarr@tedial.com> (raw)
In-Reply-To: <20040529215226.68605319.akpm@osdl.org>
On Sunday 30 May 2004 06:52, Andrew Morton wrote:
> Also there was breakage (recently fixed) in which /dev/sdaN's readahead
> setting was being inherited from the blockdev on which /dev resides. But
> reading regular files is OK.
>
I don't think I have that fix applied here.
I couldn't find any read_ahead* nor *ra_* under /sys, but blockdev works.
Btw, by default it was using a read ahead of 128 Kb (blockdev returned 256)
I re-run the dd read tests on reiserfs on the qla device (the one that took
1m27s before). These are the results on 2.6.4 :
blockdev --setra 1024 /dev/sde : 28s
(but this is the dd test in a most probably unfragmented file, so it's not a
value that can be used in real life)
blockdev --setra 512 /dev/sde : 51s (approx. what 2.4.21 took by default)
blockdev --setra 256 /dev/sde : 1m27s
blockdev --setra 128 /dev/sde : 2m9s
blockdev --setra 64 /dev/sde : 2m55s
blockdev --setra 0 /dev/sde : 13m33s
On 2.4.21:
By default, /proc/sys/vm/min-readahead is 3 and /proc/sys/vm/max-readahead is
127. I suppose those are Kb, since it didn't allow me to set a read ahead
value over 255 when using blockdev.
blockdev --setra 1024 /dev/sde : n/a (BLKRASET: Invalid argument)
blockdev --setra 512 /dev/sde : n/a (BLKRASET: Invalid argument)
blockdev --setra 256 /dev/sde : n/a (BLKRASET: Invalid argument)
blockdev --setra 255 /dev/sde : 52s
blockdev --setra 0 /dev/sde : 54s
As this was unexpected (it seems blockdev is a NOP on 2.4.21 ?), I tried
modifying /proc/sys/vm/min-readahead and max.
I set both to 512 (which should match blockdev --setra 1024 on 2.6.4) and got
25s reading
Setting both to 128kb (blockdev --setra 256), it took 49s.
Setting both to 0 (disabling read-ahead), it took 3m29s (compare that to
13m33s on 2.6.4, so definitely, there's some problem here).
Anything else I can do to help to find the problem?
--
Antonio Larrosa
Tecnologias Digitales Audiovisuales, S.L.
http://www.tedial.com
Parque Tecnologico de Andalucia . Málaga (Spain)
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2004-05-31 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200405261743.28111.antlarr@tedial.com>
[not found] ` <20040526205225.7a0866aa.akpm@osdl.org>
[not found] ` <200405281516.41901.antlarr@tedial.com>
2004-05-28 22:45 ` iowait problems on 2.6, not on 2.4 Andrew Morton
2004-05-30 0:46 ` Doug Ledford
2004-05-30 4:52 ` Andrew Morton
2004-05-31 11:24 ` Antonio Larrosa Jiménez [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=200405311324.38424.antlarr@tedial.com \
--to=antlarr@tedial.com \
--cc=akpm@osdl.org \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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