From: Vojtech Pavlik <vojtech@suse.cz>
To: Jan Kasprzak <kas@informatics.muni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE write speed (Promise versus AMD)
Date: Mon, 9 Sep 2002 13:53:25 +0200 [thread overview]
Message-ID: <20020909135325.A1125@ucw.cz> (raw)
In-Reply-To: <20020904195729.A3985@fi.muni.cz>; from kas@informatics.muni.cz on Wed, Sep 04, 2002 at 07:57:29PM +0200
On Wed, Sep 04, 2002 at 07:57:29PM +0200, Jan Kasprzak wrote:
> Hello, all!
>
> I have a machine with six identical IDE drives (WD1200BB),
> three of them connected to the on-board controller (it is AMD 768MPX chipset),
> and other three are connected to the Promise controller (PDC 20269).
> All drives are UDMA 100, read speed measured by "hdparm -t /dev/hd[abcefg]"
> is about 45 MBytes/s for every drive. However, the write speed seems
> to differ between AMD and Promise controllers. I've tried to do
>
> time sh -c 'dd if=/dev/zero of=/dev/hdX bs=1024k count=2048; sync'
>
> - it takes about 50 seconds (~40 MByte/s write speed) on hda, hdb and hdc,
> but 2 minutes 48 seconds (~12 MByte/s write speed) on hde, hdf and hdg.
> I have 1 GB of RAM, server is dual athlon 2000+. Kernel is 2.4.20-pre5-ac1.
>
> Is there any problem with the Promise IDE driver on Linux?
This looks most likely to be incorrect programming of UDMA registers on
the Promise chip. UDMA is asymmetrical by design - the hd->mb and mb->hd
speeds can be different. If you get correct read rates, it's the
harddrive that's set up correctly, for writes it's the IDE chip that has
to be programmed for the speed.
--
Vojtech Pavlik
SuSE Labs
prev parent reply other threads:[~2002-09-09 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 17:57 Jan Kasprzak
2002-09-04 23:38 ` Alan Cox
[not found] ` <001501c2546e$7e303720$6400a8c0@athlon2000>
2002-09-05 7:33 ` Jan Kasprzak
2002-09-09 11:53 ` Vojtech Pavlik [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=20020909135325.A1125@ucw.cz \
--to=vojtech@suse.cz \
--cc=kas@informatics.muni.cz \
--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
all inboxes | Powered by JetHome®