From: Tim Moore <timothymoore@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: Re: UDMA 100 / PIIX4 question
Date: Mon, 19 Mar 2001 12:17:38 -0800 [thread overview]
Message-ID: <3AB66962.2345BFB7@bigfoot.com> (raw)
In-Reply-To: <20010318165246Z131240-406+1417@vger.kernel.org> <3AB65C51.3DF150E5@bigfoot.com> <3AB65F14.26628BEF@coplanar.net>
Jeremy Jackson wrote:
>
> Tim Moore wrote:
> > 15MB/s for hdparm is about right.
>
> Yes, since hdparm -t measures *SUSTAINED* transfers... the actual "head rate" of data reads from
> disk surface. Only if you read *only* data that is alread in harddrive's cache will you get a speed
> close to the UDMA mode of the drive/controller. The cache is around 1Mbyte, so for a split-second
> re-read of some data....
Apologies for the too brief answer. Sustained real world transfer rates for the PIIX4 under ideal
setup conditions and a quiet bus are 14-18MB/s. Faster disk architecture and forcing ide driver
parameters will not change this.
Here's what you might expect from this disk family with an ATA-66 capable chipset:
[tim@abit tim]# hdparm -i /dev/hda; hdparm -tT /dev/hda
/dev/hda:
Model=IBM-DTLA-307020, FwRev=TX3OA50C, SerialNo=YH0YHF45553
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=40188960
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 udma5
/dev/hda:
Timing buffer-cache reads: 128 MB in 0.81 seconds =158.02 MB/sec
Timing buffered disk reads: 64 MB in 1.85 seconds = 34.59 MB/sec
Larger sustained transfers are about 75% of the burst/cache influenced hdparm timings.
[tim@abit tim]# time dd if=/dev/hda of=/dev/null bs=1k count=500k
512000+0 records in
512000+0 records out
0.340u 6.780s 0:19.68 36.1% 0+0k 0+0io 115pf+0w
[tim@abit tim]# echo "512000/19.68" | bc -q
26016
--
| 650.390.9613 | 6502247437@messaging.cellone-sf.com
next prev parent reply other threads:[~2001-03-19 20:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-18 16:53 UDMA 100 / PIIX4 question quintaq
2001-03-19 19:21 ` Tim Moore
2001-03-19 19:33 ` Jeremy Jackson
2001-03-19 20:17 ` Tim Moore [this message]
2001-03-19 22:22 ` quintaq
2001-03-20 16:11 ` Holger Lubitz
2001-03-20 17:33 ` Jeremy Jackson
2001-03-20 20:21 ` quintaq
2001-03-20 21:32 ` Mark Hahn
2001-03-21 9:56 ` quintaq
2001-03-21 16:26 ` quintaq
2001-03-21 16:38 ` Mike Dresser
2001-03-23 10:27 ` quintaq
2001-03-21 19:18 ` Tim Moore
2001-03-21 19:29 ` Andre Hedrick
2001-03-22 13:21 ` Holger Lubitz
2001-03-23 10:27 ` quintaq
2001-03-21 19:14 ` Tim Moore
2001-03-23 10:27 ` quintaq
2001-03-23 21:17 ` Tim Moore
2001-03-21 14:06 ` Holger Lubitz
2001-03-19 20:32 ` Mark Hahn
2001-03-19 21:51 ` Tim Moore
2001-03-19 19:55 ` Jeremy Jackson
2001-03-19 20:38 ` Tim Moore
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=3AB66962.2345BFB7@bigfoot.com \
--to=timothymoore@bigfoot.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 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.