All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Bouton <Lionel.Bouton@inet6.fr>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: 0@pervalidus.net
Subject: Re: ECS K7S5A: IDE performance
Date: Thu, 29 Aug 2002 01:02:12 +0200	[thread overview]
Message-ID: <3D6D5674.9090103@inet6.fr> (raw)
In-Reply-To: 3D6D2537.F410B52A@nortelnetworks.com

Chris Friesen wrote:

>Frédéric L. W. Meunier wrote:
>
>>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.
>>
>
>If you're reading more than the size of your on-drive buffer then you'll be limited by the speed at
>which the information can be grabbed off the drive--in your case, 38.1MB/s, which is quite good.
>
>ATA33/66/100/133 only makes a significant difference in speed when you're reading from the on-drive
>cache.
>

In fact I remember having seen something like 10-20% throughput increase 
for the same drive used in UDMA mode 4 (66MB/s) on an HPT366 and UDMA 
mode 5 (100MB/s) on a SiS735 for a drive which maxed out at around 
30/35MB/s.

This could be either caused by IDE controller/PCI interface 
(mis)behaviour, drive firmware tuned for ATA100 instead of ATA66, IDE 
bus overheads. I don't know for sure, but apparently switching from 
ATA66 to ATA100 can bring some juice in some cases where the max platter 
throughput is not even near max advertised IDE bandwidth.

Anyway, to answer to the original post, 38.1 MB/s is quite good.

LB.


  reply	other threads:[~2002-08-29  2:24 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
2002-08-28 19:32     ` Chris Friesen
2002-08-28 23:02       ` Lionel Bouton [this message]
2002-08-28 22:11     ` Daniel Egger
2002-08-28 19:09 ` Vojtech Pavlik
  -- strict thread matches above, loose matches on Subject: below --
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=3D6D5674.9090103@inet6.fr \
    --to=lionel.bouton@inet6.fr \
    --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 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.