From: Vojtech Pavlik <vojtech@suse.cz>
To: "Fr?d?ric L. W. Meunier" <0@pervalidus.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ECS K7S5A: IDE performance
Date: Wed, 28 Aug 2002 21:28:11 +0200 [thread overview]
Message-ID: <20020828212811.A20840@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0208281611210.213-100000@pervalidus.dyndns.org>; from 0@pervalidus.net on Wed, Aug 28, 2002 at 04:19:13PM -0300
On Wed, Aug 28, 2002 at 04:19:13PM -0300, Fr?d?ric L. W. Meunier wrote:
> On Wed, 28 Aug 2002, Tomas Szepe wrote:
>
> > > I have an ECS K7S5A 3.1A. It works fine with 2.4.19. No
> > > corruption. Now I tested it with hdparm and:
> > >
> > > hdparm -tT /dev/hda
> > >
> > > /dev/hda:
> > > Timing buffer-cache reads: 128 MB in 0.79 seconds =162.03 MB/sec
> > > Timing buffered disk reads: 64 MB in 1.68 seconds = 38.10 MB/sec
> > >
> > > Only 38.10 ?
> >
> > How do you mean, only 38.10?
>
> I just thought it'd be much more with an ATA100. I got more or
> less the same with my earlier motherboard, an ASUS A7APro, and
> without ATA66 - which would print a lot of CRC errors at boot
> time if enabled in the BIOS. The K7S5A doesn't print any and is
> rock solid.
>
> Maybe running it at 100/133 (and not 100/100) decreases
> performance ? I read is somewhere. I have an Athlon 1000 (200)
> with 2x256Mb DDR PC2100.
No. The limit is the drive platter read speed.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-08-28 19:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 19:00 ECS K7S5A: IDE performance Frédéric L. W. Meunier
2002-08-28 19:06 ` Tomas Szepe
2002-08-28 19:19 ` Frédéric L. W. Meunier
2002-08-28 19:28 ` Vojtech Pavlik [this message]
2002-08-28 19:32 ` Chris Friesen
2002-08-28 23:02 ` Lionel Bouton
2002-08-28 22:11 ` Daniel Egger
2002-08-28 19:09 ` Vojtech Pavlik
2002-08-29 0:05 Dieter Nützel
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=20020828212811.A20840@ucw.cz \
--to=vojtech@suse.cz \
--cc=0@pervalidus.net \
--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;
as well as URLs for NNTP newsgroup(s).