public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Lincoln Dale <ltd@cisco.com>
Cc: Baldur Norddahl <bbn-linux-kernel@clansoft.dk>,
	linux-kernel@vger.kernel.org
Subject: Re: IDE/raid performance
Date: Wed, 17 Apr 2002 17:38:54 -0700	[thread overview]
Message-ID: <20020418003854.GD574@matchmail.com> (raw)
In-Reply-To: <20020417125838.GA27648@dark.x.dtu.dk> <5.1.0.14.2.20020418082824.03112008@localhost>

On Thu, Apr 18, 2002 at 08:44:45AM +1000, Lincoln Dale wrote:
> At 02:58 PM 17/04/2002 +0200, Baldur Norddahl wrote:
> >It is clear that the 33 MHz PCI bus maxes out at 75 MB/s. Is there a reason
> >it doesn't reach 132 MB/s?
> 
> welcome to the world of PC hardware, real-world performance and theoretical 
> numbers.
> 
> in theory, a 32/33 PCI bus can get 132mbyte/sec.
> 
> in reality, the more cards you have on a bus, the more arbitration you 
> have, the less overall efficiency.
> 
> in theory, with neither the initiator or target inserting wait-states, and 
> with continual bursting, you can achieve maximum throughput.
> in reality, continual bursting doesn't happen very often and/or many 
> hardware devices are not designed to either perform i/o without some 
> wait-states in some conditions or provide continual bursting.
> 
> in short: you're working on theoretical numbers.  reality is typically far 
> far different!
> 
> 
> something you may want to try:
>   if your motherboard supports it, change the "PCI Burst" settings and see 
> what effect this has.
>   you can probably extract another 20-25% performance by changing the PCI 
> Burst from 32 to 64.

This ie a problem with the VIA chipsets.  Intel chipsets burst 4096
bytes per burst, while the VIA chipsets were sending doing 64 bytes per burst.

AMD (like the origional poster later mentioned) chipsets weren't mentioned
in the comparison article I read, so I don't know if it has the same
trouble.

Mike

      reply	other threads:[~2002-04-18  0:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 12:58 IDE/raid performance Baldur Norddahl
2002-04-17 13:43 ` Mike Dresser
2002-04-17 14:00   ` Baldur Norddahl
2002-04-17 15:15     ` nick
2002-04-17 15:48       ` Alan Cox
2002-04-17 17:27         ` Jeff V. Merkey
2002-04-17 17:47           ` Kent Borg
2002-04-17 17:48             ` nick
2002-04-17 23:26             ` Mike Fedyk
2002-04-18  6:47               ` Andre Hedrick
2002-04-18  7:41               ` Helge Hafting
2002-04-18 21:22                 ` Mike Fedyk
2002-04-17 17:36       ` Baldur Norddahl
2002-04-17 17:41         ` Mike Dresser
2002-04-17 17:46         ` nick
2002-04-17 22:35         ` dean gaudet
2002-04-17 23:52           ` Alan Cox
2002-04-17 20:36       ` Kurt Garloff
2002-04-21 19:01         ` Pavel Machek
2002-04-18 15:51       ` Bill Davidsen
2002-04-18 18:33         ` Mike Galbraith
2002-04-17 15:09 ` Bill Davidsen
2002-04-17 18:38 ` Andre Hedrick
2002-04-17 22:44 ` Lincoln Dale
2002-04-18  0:38   ` Mike Fedyk [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=20020418003854.GD574@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=bbn-linux-kernel@clansoft.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltd@cisco.com \
    /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