From: Ming Zhang <mingz@ele.uri.edu>
To: bdameron@pivotlink.com
Cc: linux-raid@vger.kernel.org
Subject: Re: More tales of horror from the linux (HW) raid crypt
Date: Wed, 22 Jun 2005 20:49:18 -0400 [thread overview]
Message-ID: <1119487758.5501.185.camel@localhost.localdomain> (raw)
In-Reply-To: <1119485655.42b9fed75fc87@mail.pivotlink.com>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Wed, 2005-06-22 at 17:14 -0700, bdameron@pivotlink.com wrote:
> Quoting Ming Zhang <mingz@ele.uri.edu>:
>
> > will this 24 port card itself will be a bottleneck?
> >
> > ming
>
> Since the card is PCI-X the only bottleneck on it might be the Processor since
> it is shared with all 24 ports. But I do not know for sure without testing it.
> I personally am going to stick with the new 16 port version. Which is a PCI-
> Express card and has twice the CPU power. Since there are so many spindles it
> should be pretty darn fast. And remember that even tho the drives are 150MBps
> they realistically only do about 25-30MBps.
the problem here is taht each HD can stably deliver 25-30MBps while the
PCI-x will not arrive that high if have 16 or 24 ports. i do not have a
chance to try out though. those bus at most arrive 70-80% the claimed
peak # :P
>
> Brad Dameron
> SeaTab Software
> www.seatab.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-23 0:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 11:47 when does it become faulty disk Raz Ben-Jehuda(caro)
2005-06-19 19:10 ` Molle Bestefich
2005-06-20 6:43 ` raz ben jehuda
2005-06-20 7:55 ` Molle Bestefich
2005-06-20 10:09 ` raz ben jehuda
2005-06-20 13:45 ` Michael Tokarev
2005-06-20 15:35 ` raz ben jehuda
2005-06-21 1:53 ` More tales of horror from the linux (HW) raid crypt Harry Mangalam
2005-06-22 19:33 ` Mike Hardy
2005-06-22 20:16 ` Harry Mangalam
2005-06-22 20:38 ` Jure Pecar
2005-06-22 21:33 ` Harry Mangalam
2005-06-22 23:15 ` SMART, was " Konstantin Olchanski
2005-06-22 23:32 ` Harry Mangalam
2005-06-22 23:35 ` Mike Hardy
2005-06-22 21:09 ` Brad Dameron
2005-06-22 21:43 ` Harry Mangalam
2005-06-22 22:00 ` Ming Zhang
2005-06-22 22:11 ` John Madden
2005-06-22 22:26 ` Ming Zhang
2005-06-23 0:20 ` bdameron
2005-06-22 22:45 ` Harry Mangalam
2005-06-22 23:05 ` Ming Zhang
2005-06-23 0:25 ` bdameron
2005-06-23 0:14 ` bdameron
2005-06-23 0:49 ` Ming Zhang [this message]
2005-06-23 3:05 ` Guy
2005-06-23 12:31 ` Ming Zhang
2005-06-23 13:03 ` Guy
2005-06-23 13:17 ` Andy Smith
2005-06-23 13:19 ` Ming Zhang
2005-06-22 23:54 ` Jon Lewis
2005-06-22 20:54 ` Dan Stromberg
2005-06-22 21:15 ` Brad Dameron
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=1119487758.5501.185.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=bdameron@pivotlink.com \
--cc=linux-raid@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).