From: "Daniel R. Warner" <drwarner@mail.myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Poor IDE performance with VIA MVP3
Date: Mon, 05 Nov 2001 12:55:09 -0500 [thread overview]
Message-ID: <3BE6D27D.6020305@mail.myrealbox.com> (raw)
In-Reply-To: <20011105005033.A10060@isis.visi.com> <01110516120000.00794@nemo> <20011105114242.A8099@isis.visi.com>
Ryan Hayle wrote:
> hdparm -T (buffer-cache reads) gives good numbers, 43v69 M/sec just
> now.
<snip>
> It's sounding more and more like this isn't a driver/chipset problem, but
> something wrong with the HD itself. Thanks for your insight.
I think that this is probably the case. I just tested a Maxtor drive on
a MVP3 on 2.4.12-ac6, 2.4.13-ac7, and 2.4.14-pre8 (all with the preempt
patch applied) and get ~8.5MB/sec on buffered disk reads, and ~55MB/sec
on buffer-cache reads.
-D
next prev parent reply other threads:[~2001-11-05 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 6:50 Poor IDE performance with VIA MVP3 Ryan Hayle
2001-11-05 16:12 ` vda
2001-11-05 17:42 ` Ryan Hayle
2001-11-05 17:55 ` Daniel R. Warner [this message]
2001-11-05 19:54 ` Mike Maravillo
2001-11-06 11:50 ` vda
[not found] ` <Pine.LNX.4.10.10111051506270.13543-100000@coffee.psychology.mcmaster.ca>
2001-11-06 5:21 ` Ryan Hayle
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=3BE6D27D.6020305@mail.myrealbox.com \
--to=drwarner@mail.myrealbox.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