From: Bas Mevissen <ml@basmevissen.nl>
To: Kyle <kyle@southa.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ICH5 with 2.6.1 very slow
Date: Thu, 05 Feb 2004 18:23:44 +0100 [thread overview]
Message-ID: <40227C20.80404@basmevissen.nl> (raw)
In-Reply-To: <164601c3ec06$be8bd5a0$b8560a3d@kyle>
Kyle wrote:
> Problem with ICH5?
> I read the list web, so please CC my email, thanks.
>
> P4 2.6G HT, 2GB Ram, ICH5, WD250GB/8M x 2 (md raid 1), kernel 2.6.1
> Timing buffer-cache reads: 128 MB in 0.14 seconds =882.89 MB/sec
> Timing buffered disk reads: 64 MB in 2.14 seconds = 29.93 MB/sec
>
> Celeron 1.3T, 1GB Ram, SIS630/5513, WD80GB/2M x 2 (md raid 1), kernel 2.6.1
> Timing buffer-cache reads: 128 MB in 1.24 seconds =103.08 MB/sec
> Timing buffered disk reads: 64 MB in 1.83 seconds = 35.00 MB/sec
>
> Celeron 2.5G, 512MB Ram, i845/ICH4, WD120GB/8M x 2 (md raid 1), redhat
> kernel 2.4.20
> Timing buffer-cache reads: 128 MB in 0.35 seconds =365.71 MB/sec
> Timing buffered disk reads: 64 MB in 1.38 seconds = 46.38 MB/sec
>
Is that a parallel IDE? I own a S-ATA IDE (also WD) with an ICH5. That
performs around 45-50MB/sec with 2.6.1. I've never tried 2.4.xx on it.
Bas.
next prev parent reply other threads:[~2004-02-05 17:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 16:40 ICH5 with 2.6.1 very slow Kyle
2004-02-05 17:23 ` Bas Mevissen [this message]
2004-02-05 17:27 ` Kyle
2004-02-05 17:30 ` Bas Mevissen
2004-02-05 17:33 ` Kyle
2004-02-06 10:10 ` Bas Mevissen
2004-02-06 21:32 ` Kyle
2004-02-09 8:32 ` Bas Mevissen
2004-02-09 8:56 ` Kyle Wong
2004-02-11 14:54 ` Kyle
2004-02-12 8:41 ` Jamie Lokier
2004-02-12 14:08 ` Kyle
2004-02-12 14:32 ` Bas Mevissen
2004-02-12 19:28 ` Jeff Garzik
2004-02-13 3:40 ` Kyle
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 10:50 Daniel Blueman
2004-02-15 18:48 Kyle
2004-02-15 19:19 ` Bartlomiej Zolnierkiewicz
2004-02-15 19:23 ` Martin Schlemmer
2004-02-16 13:58 ` Kyle
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=40227C20.80404@basmevissen.nl \
--to=ml@basmevissen.nl \
--cc=kyle@southa.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