linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bdameron@pivotlink.com
To: linux-raid@vger.kernel.org
Subject: Re: More tales of horror from the linux (HW) raid crypt
Date: Wed, 22 Jun 2005 17:25:50 -0700	[thread overview]
Message-ID: <1119486350.42ba018edc4b8@mail.pivotlink.com> (raw)
In-Reply-To: <200506221545.05840.hjm@tacgi.com>

I read this article some time ago. Note that they were testing the older Areca 
card with it's first firmware version. The new PCIe card has twice the CPU 
power and has worked out their initial bugs. The performance is enourmously 
improved. However the price is quit a lot higher than most. 

Brad Dameron
SeaTab Software
www.seatab.com


Quoting Harry Mangalam <hjm@tacgi.com>:

> Also a good point - I was just discussing this in another thread.
> Areca makes a number of SATA RAID controllers - some are SCSI-SATA, some are
> 
> PCI-X-SATA, some are PCIe-SATA.  
> 
> Areca supplied this URL to a relatively long review of recent SATA and SCSI 
> controllers - it's worth a read.  And surprisingly, the SATA controllers do 
> pretty well against the SCSI controllers.
> 
> http://www.tweakers.net/reviews/557/1
> 
> hjm
> 
> On Wednesday 22 June 2005 3:00 pm, Ming Zhang wrote:
> > will this 24 port card itself will be a bottleneck?
> >
> > ming
> >
> 
> -- 
> Cheers, Harry
> Harry J Mangalam - 949 856 2847 (vox; email for fax) - hjm@tacgi.com 
>             <<plain text preferred>>
> -
> 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
> 




  parent reply	other threads:[~2005-06-23  0:25 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 [this message]
2005-06-23  0:14             ` bdameron
2005-06-23  0:49               ` Ming Zhang
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=1119486350.42ba018edc4b8@mail.pivotlink.com \
    --to=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).