From: Holger Lubitz <h.lubitz@internet-factory.de>
To: linux-kernel@vger.kernel.org
Subject: Re: UDMA 100 / PIIX4 question
Date: Thu, 22 Mar 2001 14:21:29 +0100 [thread overview]
Message-ID: <3AB9FC59.92C97ACE@internet-factory.de> (raw)
In-Reply-To: <20010321095533Z131410-407+1932@vger.kernel.org> <Pine.LNX.4.10.10103211000370.29537-100000@master.linux-ide.org>
Andre Hedrick wrote:
> You may get a burst because of caching prefetch or predictive readahead,
> but that is artifical; however, in your case the root directory begins 25%
> in the drive.
But still it gives faster transfers than /dev/hda. The question is why.
I do not think that factor 2 can be explained by prefetch or readahead
alone.
> First you have the faster portion of the drive using a lame OS, so do not
> expect Linux to perform if you put it on the slowest portions of the
> device.
:-) But putting it at the beginning at least leaves the linux partitions
together.
Having the root fs in the outermost partition might give slightly faster
transfers, but slightly longer seeks to get there.
> [root@via DiskPerf-1.0.3]# ./DiskPerf /dev/hda
Is that an unreleased version? kernel.org still has 1.0.1.
Holger
next prev parent reply other threads:[~2001-03-22 13:22 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 [this message]
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=3AB9FC59.92C97ACE@internet-factory.de \
--to=h.lubitz@internet-factory.de \
--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