From: Greg Freemyer <greg.freemyer@gmail.com>
To: GrantC <grant_nospam@dodo.com.au>
Cc: linux-ide@vger.kernel.org
Subject: Re: IDE channels not independent in PIIX4E?
Date: Fri, 25 Feb 2005 09:45:37 -0500 [thread overview]
Message-ID: <87f94c37050225064563f663c5@mail.gmail.com> (raw)
In-Reply-To: <e6dt11lj3pt9v7hl0luqseris0fs2kvr7v@4ax.com>
I can't speak to your specific motherboard/chipset, but the
performance testing I have done shows that the onboard IDE controllers
do not have two independent channels, so using both channels does not
provide twice the speed of a single channel, not even close.
True under both Linux and Windows2K.
OTOH, I have tested 3 or 4 PCI-based Dual Channel IDE controllers and
they work much better from a performance perspective. I recently
tested both the SIIG dual-channel card and Adaptec dual-channel card.
They were both in the $50-$60 range and neither has given me any
problems, but I have heard people complain about the SIIG.
HTH
Greg
On Fri, 25 Feb 2005 16:47:46 +1100, GrantC <grant_nospam@dodo.com.au> wrote:
> Greetings,
>
> I have an old but reliable Intel SE440BX-2 with 440BX and PIIX4E
> chipset. 120 + 80 GB hard drives on each channel as master, very
> disappointing md software RAID0 or RAID1 performance.
>
> Slackware 10.1 with 2.4.29 or 2.4.30pre2, testing back to 2.4.21.
>
> One thing I noticed is that if I start a
>
> dd if=/dev/zero bs=4k of=/dev/hdX
>
> on each drive, then Ctrl-C stop each, one terminal will wait for
> the other drive to complete the write before starting its turn
> to complete the pending write.
>
> It seems that somewhere what I expected to be two parallel data
> streams are serialised. As the chipset only does udma33 I was
> hoping to get an OS performance gain with RAID0. Box has 512MB
> memory and rarely touches swap.
>
> Is this a limit of the hardware or did I miss some kernel tuning?
>
> Have benchmarked with tiobench -- that tells me chunk-size has
> little effect, software RAID costs about 8% CPU, and sequential
> writes cost roughly 20%, 40% and 60% for ext2, ext3 and reiserfs.
>
> Filesystem sequential read speed improved from 17 to 25 MB/s for
> RAID0, but no improvement in write speed.
>
> Raw (non-filesystem) dd speeds are about 27MB/s read, 20MB/s write
> to non-RAID partition. All testing done on same partitions, so
> no confusion with fast or slow end of drive. The drives are
> Seagate 7200.7 series with 2MB cache.
>
> Any pointers on tuning options appreciated, the Intel datasheets
> don't really tell me much. As for reading the kernel source, I
> have no idea where to start, not much under Docs, and I dunno
> which or which way to turn the 'knobs'.
>
> Even search terms would be welcome :)
>
> Thanks,
> Grant.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2005-02-25 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 5:47 IDE channels not independent in PIIX4E? GrantC
2005-02-25 14:45 ` Greg Freemyer [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=87f94c37050225064563f663c5@mail.gmail.com \
--to=greg.freemyer@gmail.com \
--cc=grant_nospam@dodo.com.au \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).