linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: subscribe@brmiller.ca
Cc: linux-raid@vger.kernel.org
Subject: Re: How many disks per SATA-II bus?
Date: Tue, 29 Jan 2008 14:15:24 -0500	[thread overview]
Message-ID: <479F7B4C.7000602@garzik.org> (raw)
In-Reply-To: <214675.77163.qm@web88308.mail.re4.yahoo.com>

Bruce Miller wrote:
> The beginning of Section 4 of the Linux Sotfware-RAID-HOWTO
> states emphatically that "you should only have one device per
> IDE bus. Running disks as master/slave is horrible for
> performance. IDE is really bad at accessing more that one drive
> per bus".
> 
> Do the same cautions apply to building a RAID array using
> SATA-II disks?

SATA is a point-to-point serial connection, totally different technology.

	Jeff




      reply	other threads:[~2008-01-29 19:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 18:25 How many disks per SATA-II bus? Bruce Miller
2008-01-29 19:15 ` Jeff Garzik [this message]

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=479F7B4C.7000602@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=subscribe@brmiller.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).