From: <pcg@goof.com ( Marc) (A.) (Lehmann )>
To: linux-kernel@vger.kernel.org
Subject: Re: I/O very slow under 2.4 (device reading)
Date: Thu, 9 Aug 2001 04:34:31 +0200 [thread overview]
Message-ID: <20010809043431.C2456@cerebro.laendle> (raw)
On Wed, Aug 08, 2001 at 11:12:45AM -0700, Linus Torvalds <torvalds@transmeta.com> wrote:
> and the VM disagree about how/when to allocate memory. It's fixed by the patch
> I'll make a real pre-patch (2.4.8-pre7) with the full changeset, can you
after 10 gigs of reading:
procs memory swap io system cpu
r b w swpd free buff cache si so bi bo in cs us sy id
0 1 0 0 6828 372696 36340 0 0 48292 6 726 2188 0 25 75
0 1 0 0 6880 370536 39352 0 0 33792 0 726 3725 1 37 62
1 0 1 0 6880 370160 36340 0 0 25652 48 411 3374 1 82 17
0 1 0 0 6628 370780 36288 0 0 44788 0 690 2071 1 31 68
1 0 1 0 6832 372972 36264 0 0 41988 0 674 2933 0 42 57
the system still feels a bit sluggishly, but otherwise NO SIGN of that
problem (no io slowdown, no short freezes). just the usual "disks are
in-use" contentions.
cool ,)
> at a nice stable 21MB/s which is all my disk can deliver.
you _should_ know that raw speed doesn't mean too much.
> [ Damn, maybe I should get one of those nice big 7200 rpm IBM drives ]
maybe noisier. and for some reason (I swear for ibm drives usually), they
keep getting uncorrectable media errors on all of my machines.. ;) still
they are the best ones available ;)
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
next reply other threads:[~2001-08-09 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 2:34 Lehmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-08 17:31 Lehmann
2001-08-08 18:12 ` Linus Torvalds
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=20010809043431.C2456@cerebro.laendle \
--to=pcg@goof.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 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®