From: Vojtech Pavlik <vojtech@suse.cz>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: Brian <hiryuu@envisiongames.net>, linux-kernel@vger.kernel.org
Subject: Re: Two hdds on one channel - why so slow?
Date: Wed, 2 Jan 2002 19:41:50 +0100 [thread overview]
Message-ID: <20020102194150.A14140@suse.cz> (raw)
In-Reply-To: <0GPA00BK988OBK@mtaout45-01.icomcast.net> <Pine.LNX.4.33.0201021808490.9573-100000@dark.pcgames.pl>
In-Reply-To: <Pine.LNX.4.33.0201021808490.9573-100000@dark.pcgames.pl>; from ole@ans.pl on Wed, Jan 02, 2002 at 06:21:25PM +0100
On Wed, Jan 02, 2002 at 06:21:25PM +0100, Krzysztof Oledzki wrote:
>
>
> On Tue, 1 Jan 2002, Brian wrote:
>
> > This is an inherent quirk (SCSI folks would say brain damage) in IDE.
> >
> > Only one drive on an IDE chain may be accessed at once and only one
> > request may go to that drive at a time. Therefore, the maximum you could
> > hope for in that test is half speed on each. Throw in the overhead of
> > continuously hopping between them and 12MB is no surprise.
>
> So?!? This ATA100 and ATA133 standards do not make any sens? It is not
> possible to have more than 66 MB/sec with on drive and is seems that it is
> not possible to use more than ~30MB/sek of 100 or 133 MB/sec ATA100/133
> bus speed with two HDDs. Oh :(((
>
> Another question - why ATA100/ATA66 HDDs are so slow with UDMA33?
> With new IBM 60 GB IC35L060AVER07-0 I have much more than 33 MB/sec with
> ATA100 and only 24 MB/sec with UDMA33 (Asus P2B with IntelBX). New 80GB Seagates
> (Baracuda IV) have the same problem.
Actually 24 MB/sec is quite a miracle with UDMA33. I'd expect values
around 16 MB/sec. Because, as far as I know, unlike SCSI, IDE doesn't do
concurrent reads and transfers (except for readahead), effectively
halving the interface transfer speed.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-01-02 18:42 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 22:34 Two hdds on one channel - why so slow? Krzysztof Oledzki
2002-01-01 23:07 ` Brian
2002-01-01 23:32 ` Andre Hedrick
2002-01-02 0:52 ` H. Peter Anvin
2002-01-02 1:19 ` Benjamin LaHaise
2002-01-02 1:24 ` H. Peter Anvin
2002-01-02 2:03 ` Benjamin LaHaise
2002-01-02 4:13 ` Andre Hedrick
2002-01-02 17:21 ` Krzysztof Oledzki
2002-01-02 18:41 ` Vojtech Pavlik [this message]
2002-01-02 19:31 ` Andre Hedrick
2002-01-02 20:23 ` Brian
2002-01-02 23:30 ` Ricky Beam
2002-01-03 1:52 ` Mark Hahn
2002-01-03 5:57 ` Ricky Beam
2002-01-04 2:54 ` Petro
2002-01-04 3:04 ` Arnaldo Carvalho de Melo
2002-01-04 4:29 ` ASUS KT266A/VT8233 board and UDMA setting Dmitri Pogosyan
2002-01-04 9:25 ` Vojtech Pavlik
2002-01-04 10:35 ` Alan Cox
2002-01-04 10:28 ` Vojtech Pavlik
2002-01-04 11:20 ` Alan Cox
2002-01-04 13:37 ` Ville Herva
2002-01-04 16:48 ` David Rees
2002-01-04 17:00 ` Alan Cox
2002-01-05 19:20 ` Dmitri Pogosyan
2002-01-05 7:20 ` Dmitri Pogosyan
2002-01-04 18:19 ` Two hdds on one channel - why so slow? Stephan von Krawczynski
2002-01-04 18:38 ` Alan Cox
2002-01-04 18:30 ` Stephan von Krawczynski
2002-01-05 0:52 ` J.A. Magallon
2002-01-05 9:41 ` Nick Holloway
2002-01-05 12:04 ` Henning P. Schmiedehausen
2002-01-05 1:28 ` Andre Hedrick
2002-01-08 23:59 ` Ricky Beam
2002-01-09 0:10 ` Mark Hahn
2002-01-09 15:27 ` Andre Hedrick
2002-01-09 16:25 ` MTBF Was: " Richard B. Johnson
2002-01-08 23:46 ` Ricky Beam
2002-01-07 8:11 ` Stevie O
2002-01-07 15:57 ` Thomas Molina
2002-01-07 16:14 ` Ricky Beam
2002-01-07 16:40 ` Thomas Molina
2002-01-07 22:23 ` Ancient Memories [was: Two hdds on one channel - why so slow?] Edesio Costa e Silva
2002-01-07 23:18 ` M. Edward (Ed) Borasky
2002-01-07 18:48 ` Two hdds on one channel - why so slow? Andre Hedrick
2002-01-07 20:19 ` Petro
2002-01-07 22:31 ` Dmitri Pogosyan
2002-01-08 13:50 ` Alan Cox
2002-01-08 14:45 ` Mike Dresser
2002-01-08 14:57 ` James A Sutherland
2002-01-08 17:15 ` Wakko Warner
2002-01-02 21:23 ` Jeffrey W. Baker
-- strict thread matches above, loose matches on Subject: below --
2002-01-03 15:49 Dana Lacoste
2002-01-03 16:44 ` Mark Hahn
[not found] <Pine.LNX.4.33.0201021452120.8693-100000@coffee.psychology.mcmaster.ca>
2002-01-04 9:28 ` Krzysztof Oledzki
2002-01-04 14:02 Jesse Pollard
2002-01-04 16:33 ` Bernd Eckenfels
[not found] ` <Pine.LNX.4.43.0201041154010.14678-100000@filesrv1.baby-dragons.com>
2002-01-04 17:14 ` Bernd Eckenfels
2002-01-04 17:22 ` Timothy Covell
2002-01-04 18:40 ` Bernd Eckenfels
2002-01-04 19:32 ` Jeffrey W. Baker
2002-01-05 12:02 ` Henning P. Schmiedehausen
2002-01-04 20:29 ` Timothy Covell
2002-01-08 23:49 ` Ricky Beam
2002-01-09 0:50 ` Timothy Covell
2002-01-09 1:22 ` Ricky Beam
2002-01-04 17:40 ` Jesse Pollard
2002-01-08 12:41 ` Rob Landley
2002-01-08 21:18 ` William Park
2002-01-09 10:56 ` Rob Landley
2002-01-09 19:50 ` William Park
[not found] <Pine.LNX.4.33.0201040844130.14385-100000@coffee.psychology.mcmaster.ca>
2002-01-04 17:18 ` Krzysztof Oledzki
2002-01-04 19:29 Dana Lacoste
2002-01-05 11:58 ` Henning P. Schmiedehausen
2002-01-05 12:20 ` Petro
2002-01-09 0:04 ` Ricky Beam
2002-01-07 17:06 Jesse Pollard
2002-01-07 17:17 ` Tommy Reynolds
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=20020102194150.A14140@suse.cz \
--to=vojtech@suse.cz \
--cc=hiryuu@envisiongames.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ole@ans.pl \
/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.