From: "Kyle" <kyle@southa.com>
To: "Bas Mevissen" <ml@basmevissen.nl>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: ICH5 with 2.6.1 very slow
Date: Fri, 6 Feb 2004 01:33:17 +0800 [thread overview]
Message-ID: <168301c3ec0e$24698be0$b8560a3d@kyle> (raw)
In-Reply-To: 40227D9D.2070704@basmevissen.nl
hdparm /dev/hda
/dev/hda:
multcount = 16 (on)
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 30401/255/63, sectors = 488397168, start = 0
tried with hdparm -a8192 /dev/hda, not much different
/dev/hdc same as /dev/hda
Kyle
----- Original Message -----
From: "Bas Mevissen" <ml@basmevissen.nl>
To: "Kyle" <kyle@southa.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, February 06, 2004 1:30 AM
Subject: Re: ICH5 with 2.6.1 very slow
> Kyle wrote:
>
> > Yes they are PATA, I expect something like 40-50MB/s, now my much slower
> > Celeron 1.3T with 80GB/2M perform better than my ICH5!
> >
>
> What does 'hdparm /dev/hdX' say (X=a,b,c...)?
>
> Bas.
>
>
>
next prev parent reply other threads:[~2004-02-05 17:29 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
2004-02-05 17:27 ` Kyle
2004-02-05 17:30 ` Bas Mevissen
2004-02-05 17:33 ` Kyle [this message]
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='168301c3ec0e$24698be0$b8560a3d@kyle' \
--to=kyle@southa.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ml@basmevissen.nl \
/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.