linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Scobie <richard@sauce.co.nz>
To: linux-ide@vger.kernel.org
Subject: Re: Resets on sil3124 & sil3726 PMP
Date: Tue, 04 Sep 2007 09:21:59 +1200	[thread overview]
Message-ID: <46DC7AF7.1010304@sauce.co.nz> (raw)
In-Reply-To: <20070903203441.GF23498@curie-int.orbis-terrarum.net>

Robin H. Johnson wrote:

> The single PMP numbers they have (under "Addonics ADSA3GPX8-4EM Striped RAID Set
> Performance Comparison") has Write=211MB/sec Read=231MB/sec.

True. I wonder if the bus spec of 3Gb/s is somewhat optimistic in the 
real world - a bit like saying one can get 132MB/s from a 32bit 33MHz 
PCI bus.

The absolute ideal throughput for 1.5 Gb/s would be 187MB/s, so the 
throughput figures above mean the link must be at 3Gb/s, it's just not 
inpressive, given that the 5 drives can do at least 300MB/s and the 
theoretical maximum for 3Gb/s is 375MB/s.

In another test at the same site, a Marvell 88SX7042 based card gets 
slightly better throughput - 196.8 write 251 read:

http://www.amug.org/amug-web/html/amug/reviews/articles/sonnet/e4p/

Looking at the graphs towards the end of the article "Seagate 160GB 
7200.9 Port Multiplier Write/Read Performance", it looks as though 
better performance may be had by distributing disks across multipole PM 
ports, rather than all on one - see 5 drives on one PM v 4 drives, each 
on it's own PM.

There are quite a number of tests of many PM cards and enclosures here:

http://www.amug.org/amug-web/html/amug/reviews/reviews.html

Regards,

Richard

  reply	other threads:[~2007-09-03 21:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-03 19:39 Resets on sil3124 & sil3726 PMP Richard Scobie
2007-09-03 20:34 ` Robin H. Johnson
2007-09-03 21:21   ` Richard Scobie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-27  8:08 Richard Scobie
2007-08-27 22:49 ` Robin H. Johnson
2007-08-27  4:55 Richard Scobie
2007-08-27  7:11 ` Petr Vandrovec
2007-09-03  8:59   ` Tejun Heo
2007-09-03  9:57     ` Petr Vandrovec
2007-09-03 12:50       ` Tejun Heo
2007-09-04  1:38         ` Petr Vandrovec
2007-09-05 12:08           ` Petr Vandrovec
2007-09-05 21:30             ` Robin H. Johnson
2007-09-06  9:52               ` Petr Vandrovec
2007-09-06 18:02                 ` Tejun Heo
2007-09-06 17:59             ` Tejun Heo
2007-08-15 13:58 Rusty Conover
2007-08-17 18:06 ` Tejun Heo
2007-08-20 19:56   ` Rusty Conover
2007-08-21  2:42     ` Rusty Conover
2007-08-22  3:03       ` Tejun Heo
2007-08-22  5:00         ` Rusty Conover
2007-08-22  5:43           ` Tejun Heo
2007-08-22  6:11             ` Rusty Conover
2007-08-22  6:39               ` Tejun Heo
2007-08-22  6:56                 ` Rusty Conover
2007-08-22  7:02                   ` Tejun Heo
2007-08-22  7:49                     ` Rusty Conover
2007-08-25  2:19                       ` Tejun Heo
2007-08-26 16:37                         ` Rusty Conover
2007-08-27  1:18                           ` Tejun Heo
2007-08-14 23:39 Rusty Conover
2007-08-15  6:10 ` Tejun Heo

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=46DC7AF7.1010304@sauce.co.nz \
    --to=richard@sauce.co.nz \
    --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).