All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Moore <timothymoore@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: Re: UDMA 100 / PIIX4 question
Date: Mon, 19 Mar 2001 12:38:37 -0800	[thread overview]
Message-ID: <3AB66E4D.5B7E3E7B@bigfoot.com> (raw)
In-Reply-To: <20010318165246Z131240-406+1417@vger.kernel.org> <3AB65C51.3DF150E5@bigfoot.com> <3AB66449.5F5C673F@coplanar.net>

> You should be able to get about 30 MB/s at the start of the disk (zone 0) according to IBM's datasheet at
> 
> http://ssdweb01.storage.ibm.com/techsup/hddtech/prodspec/dtla_spw.pdf
> 
> so if you were testing say /dev/hda1 which is at the start of the disk it should be faster.

"should be" is yes and yes, but you will not see 30MB/s and there is no actual difference between
/dev/hda and /dev/had1.

> Try hdparm -i /dev/hda (or whatever) .. . note the reported MaxMultSect= value,
> and put it in place of X in command:
> 
> hdparm -u 1 -d 1 -m X -c 1 /dev/hda

I've spent more time with real world data transfer testing than god, both PIIX4-based motherboards
and network based (Network Appliance <-> linux).  The only hdparm parameter that makes any
measurable, significnat difference for most modern drive and chipset combinations is -d1 and the
correct UDMA mode.

Try partitioning your disk in 4 equal segments and run multiple tests in runlevel1 on /dev/hda[1-4]
for '/usr/bin/time hdparm -tT' plus permutations of -a[0248]c[013]m[024816]u[01],
and /usr/bin/time dd if=/dev/hda[1-4] of=/dev/null bs=1k count={32,64,128,256,512,1024}k.

rgds,
tim.
--

      reply	other threads:[~2001-03-19 20:39 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
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 [this message]

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=3AB66E4D.5B7E3E7B@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.