From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: I/O very slow under 2.4 (device reading)
Date: Wed, 8 Aug 2001 18:12:40 +0000 (UTC) [thread overview]
Message-ID: <9krveo$82c$1@penguin.transmeta.com> (raw)
In-Reply-To: <20010808193158.A4055@cerebro.laendle>
In article <20010808193158.A4055@cerebro.laendle>,
<pcg@goof.com ( Marc) (A.) (Lehmann )> wrote:
>It might be vm related, it might be not, but I get very funny effects when
>running:
>
> buffer -S1m -s128k -m32m </dev/hde >/dev/null
>
>(buffer is just a fast read/write buffer reading stdin to stdout, i use it
>to check wether all sectors of a disk are readable, it's similar to dd,
>which creates the same effects).
I bet it's the same thing that made writes slow - the buffer allocator
and the VM disagree about how/when to allocate memory. It's fixed by the patch
that's floating around in the "VM suckage" thread along with the tweak
to fix "zone_free_plenty()".
I'll make a real pre-patch (2.4.8-pre7) with the full changeset, can you
test that out? I did an equivalent "dd" that you see problems with, and
on my current kernel as long as there isn't other IO activity it stays
at a nice stable 21MB/s which is all my disk can deliver.
[ Damn, maybe I should get one of those nice big 7200 rpm IBM drives ]
Linus
next prev parent reply other threads:[~2001-08-08 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 17:31 I/O very slow under 2.4 (device reading) Lehmann
2001-08-08 18:12 ` Linus Torvalds [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-09 2:34 Lehmann
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='9krveo$82c$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--cc=linux-kernel@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 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.