From: Mark Lord <liml@rtr.ca>
To: Richard Scobie <r.scobie@clear.net.nz>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: SAS v SATA interface performance
Date: Sat, 01 Dec 2007 22:49:00 -0500 [thread overview]
Message-ID: <47522B2C.2010205@rtr.ca> (raw)
In-Reply-To: <47522A45.50706@rtr.ca>
Oh, more fiction:
> Because SATA uses point-to-point connectivity, the scaling
> available with SAS controllers is not possible with SATA
> controllers. SATA drives must be connected on a one-to-one
> basis with the SATA connectors on the controller – i.e, a fourport
> SATA controller can connect up to four drives, an eight-port
> SATA controller can connect up to eight drives, etc. This means
> that the number of drives needed must be known prior to
> purchasing a SATA controller, or additional hardware costs will
> be incurred.
Ignoring port multipliers (hubs) again there.
A SATA hub can connect up to 31 drives to a single SATA port,
or up to 248 drives per 8-port PCI(X/e) controller card.
I don't know if anyone currently sells a 31-port multiplier, though.
Cheers
next prev parent reply other threads:[~2007-12-02 3:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 19:19 SAS v SATA interface performance Richard Scobie
2007-11-30 21:24 ` Michael Tokarev
2007-11-30 23:17 ` Alan Cox
2007-12-01 7:43 ` Richard Scobie
2007-12-01 14:37 ` Greg Freemyer
2007-12-01 19:19 ` Richard Scobie
2007-12-01 20:01 ` Mark Lord
2007-12-01 20:40 ` Jeff Garzik
2007-12-01 23:55 ` Richard Scobie
2007-12-02 3:45 ` Mark Lord
2007-12-02 3:49 ` Mark Lord [this message]
2007-12-10 7:33 ` Tejun Heo
2007-12-10 14:36 ` Jens Axboe
2007-12-10 16:28 ` Mark Lord
2007-12-10 14:50 ` James Bottomley
2007-12-10 16:32 ` Mark Lord
-- strict thread matches above, loose matches on Subject: below --
2007-12-01 0:04 Richard Scobie
2007-12-01 0:17 ` Alan Cox
2007-12-01 3:06 ` Mark Lord
2007-12-10 7:15 ` Tejun Heo
2007-12-10 16:23 ` Mark Lord
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=47522B2C.2010205@rtr.ca \
--to=liml@rtr.ca \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=r.scobie@clear.net.nz \
/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).