From: Roman Mamedov <rm@romanrm.ru>
To: Ed W <lists@wildgooses.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: HBA Adaptor advice
Date: Thu, 19 May 2011 18:36:08 +0600 [thread overview]
Message-ID: <20110519183608.2c377538@natsu> (raw)
In-Reply-To: <4DD50C89.8060006@wildgooses.com>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
On Thu, 19 May 2011 13:26:49 +0100
Ed W <lists@wildgooses.com> wrote:
> Hi, following on from a recent thread, can folks with decent multi-port
> HBA adaptors please chime in with some model numbers of known decent
> adaptors please?
Here is a useful link for you: http://blog.zorinaq.com/?e=10
> And to avoid:
> - Marvel controllers?
There are two kinds (families?) of Marvell SATA chips, and those using the
"sata_mv" module do work fine. It seems like all the complaints are directed
at the other kind, supported via "mvsas".
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-19 12:36 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 12:26 HBA Adaptor advice Ed W
2011-05-19 12:36 ` Roman Mamedov [this message]
2011-05-19 12:43 ` Mathias Burén
2011-05-19 14:06 ` Michael Sallaway
2011-05-19 19:10 ` Thomas Harold
2011-05-19 21:12 ` Rudy Zijlstra
2011-05-19 21:07 ` Brad Campbell
2011-05-20 20:58 ` Tobias McNulty
2011-05-20 21:23 ` Brad Campbell
2011-05-20 2:08 ` Andy Smith
2011-05-20 5:30 ` Stan Hoeppner
2011-05-21 9:52 ` Ed W
2011-05-20 7:33 ` Ed W
2011-05-20 10:21 ` Stan Hoeppner
2011-05-21 11:17 ` Ed W
2011-05-21 11:29 ` Rudy Zijlstra
2011-05-21 11:54 ` Ed W
2011-05-21 17:37 ` Leslie Rhorer
2011-05-22 9:41 ` Stan Hoeppner
2011-05-22 10:03 ` Rudy Zijlstra
2011-05-23 9:32 ` Ed W
2011-05-21 17:05 ` Leslie Rhorer
2011-05-22 9:04 ` Stan Hoeppner
2011-05-22 10:09 ` Brad Campbell
2011-05-22 19:25 ` Stan Hoeppner
2011-05-22 20:57 ` Tobias McNulty
2011-05-22 21:13 ` Johannes Truschnigg
2011-05-23 9:48 ` Ed W
2011-05-23 10:44 ` John Robinson
2011-05-22 23:19 ` Brad Campbell
2011-05-23 4:09 ` Roman Mamedov
2011-05-23 5:54 ` Brad Campbell
2011-05-23 6:08 ` Roman Mamedov
2011-05-23 10:42 ` Stan Hoeppner
2011-05-23 11:35 ` David Brown
2011-05-23 6:54 ` Stan Hoeppner
2011-05-23 7:23 ` Brad Campbell
2011-05-22 23:44 ` Brad Campbell
2011-05-23 0:07 ` Brad Campbell
2011-05-23 5:30 ` Stefan /*St0fF*/ Hübner
2011-05-23 10:18 ` Ed W
2011-05-23 9:58 ` Stan Hoeppner
2011-05-23 10:33 ` Ed W
2011-05-23 11:21 ` Stan Hoeppner
2011-05-20 12:18 ` Joe Landman
2011-05-20 12:34 ` Roman Mamedov
2011-05-20 12:36 ` Mathias Burén
2011-05-20 12:48 ` Joe Landman
2011-05-20 13:21 ` Ed W
2011-05-20 14:23 ` Joe Landman
2011-05-20 20:01 ` Andy Smith
2011-05-20 20:12 ` Stan Hoeppner
2011-05-20 20:24 ` Drew
2011-05-20 20:58 ` Stan Hoeppner
[not found] ` <4DD7A100.2010807@wildgooses.com>
2011-05-22 8:13 ` Stan Hoeppner
-- strict thread matches above, loose matches on Subject: below --
2011-05-23 2:11 Jim Schatzman
2011-05-23 3:39 ` Tobias McNulty
2011-05-23 10:42 ` Ed W
2011-05-23 11:14 HBA Adaptor Advice Ed W
2011-05-23 11:55 ` Joe Landman
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=20110519183608.2c377538@natsu \
--to=rm@romanrm.ru \
--cc=linux-raid@vger.kernel.org \
--cc=lists@wildgooses.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;
as well as URLs for NNTP newsgroup(s).