linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Sander <sander@humilis.net>,
	linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: [OT] 8-port AHCI SATA Controller?
Date: Wed, 1 Feb 2006 11:03:32 +0100	[thread overview]
Message-ID: <20060201100332.GA14960@favonius> (raw)
In-Reply-To: <20060131185804.GM18970@csclub.uwaterloo.ca>

Lennart Sorensen wrote (ao):
> On Tue, Jan 31, 2006 at 07:50:07PM +0100, Sander wrote:
> > Actually, I need 24 ports :-)  But 3x SX8 sets me back 540 dollars
> > according to pricewatch, which is less than half.
> 
> I know with older promise controllers, it wasn't possible to run more
> than 2 in one system as far as I remember due to some dma issues.  Not
> sure if that applies to the SX8.
> 
> If it turns out the SX8 has issues (like the one pointed out earlier
> about number of commands to the card at once) or that it can't have 3
> cards in one system at once, then what?  Are you then out $540 + the
> cost of a better controller?  Certainly worth finding out before
> spending the money.

I have a few systems which need 24 ports, so I could spread them, but
you are right of course.

> > Fakeraid controllers are less expensive, and would do too of course :-)
> 
> Of course those aren't hardware, and are only meant for small toy raids
> for windows users. The rest of use treat them as ide/sata controllers
> only.

Exactly what I need (and am looking for). An 8+ sata controller. I would
not use the fakeraid.

> I haven't seen one of those with more than 4 ports either. If
> the SX8 is one, then I must admit I haven't looked at it before. I try
> to avoid hardware from promise whenever possible.

I did too, but their attitude towards Linux seems to have changed, and I
am pretty pleased with their SATA150 TX4.

	Kind regards, Sander

-- 
Humilis IT Services and Solutions
http://www.humilis.net

  parent reply	other threads:[~2006-02-01 10:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 11:53 [OT] 8-port AHCI SATA Controller? Sander
2006-01-31 16:39 ` Lennart Sorensen
2006-01-31 17:17   ` Sander
2006-01-31 18:30     ` Lennart Sorensen
2006-01-31 18:39       ` Sander
2006-01-31 18:44         ` Lennart Sorensen
2006-01-31 18:50           ` Sander
2006-01-31 18:58             ` Lennart Sorensen
2006-01-31 20:48               ` Roger Heflin
2006-02-01 10:15                 ` Sander
2006-02-01 14:53                   ` Roger Heflin
2006-02-01 10:03               ` Sander [this message]
2006-01-31 18:40       ` Joel Jaeggli
2006-01-31 18:51         ` Sander
2006-01-31 18:19 ` Joshua Kugler
2006-01-31 18:56   ` Sander
2006-01-31 19:02     ` Joshua Kugler
2006-02-01 10:18       ` Sander
2006-01-31 20:38     ` Jens Axboe
2006-01-31 20:48       ` Joshua Kugler
2006-01-31 20:59         ` Jens Axboe
2006-01-31 21:31           ` Joshua Kugler
2006-02-01 16:13   ` Bill Davidsen
2006-02-01 19:15     ` Joshua Kugler

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=20060201100332.GA14960@favonius \
    --to=sander@humilis.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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).