linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Stuart D. Gathman" <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM on SATA/PATA disks
Date: Sat, 12 May 2007 21:34:16 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0705122130070.27083-100000@bmsred.bmsi.com> (raw)
In-Reply-To: <1179019386.15162.53.camel@pc.ilinx>

On Sat, 12 May 2007, Brian J. Murrell wrote:

> On Sat, 2007-05-12 at 21:12 -0400, Stuart D. Gathman wrote:
> > 
> > The interrupt rate has nothing to do with the type of disk, and a lot to
> > do with the controller.  There is a CPU difference between $50 
> > consumer IDE/SATA adapters, and $300 server grade IDE/SATA adapters.
> > You'll want the controller to support fast DMA at minimum.
> 
> I thought the biggest thing that SCSI had that IDE didn't was SCSI's
> ability to shovel an ass-barn-load of data to a disk and the disk would
> go deal with it, giving up the SCSI bus so that another disk could be
> shovelled another ass-barn-load of data to go and deal with, and so on.
> 
> ...
> 
> The contrast with IDE (or PATA as I guess the trendy name is), again as
> I always thought was that the IDE bus was not available for use while a
> disk was still pending a media I/O operation, so that with multiple
> devices, you could not leverage the I/O of the IDE bus using multiple
> devices, essentially in parallel.  I guess this is where having system
> with multiple IDE buses and only putting a single device per bus grew
> from.

We always put exactly one IDE disk per channel for that very reason.
You are correct that with 2 disks on the same channel, only one can
be active at a time.  So don't do that.  A $50 IDE PCI card give you 2 IDE
channels - for 2 disks in high performance mode (suitable for mirroring).
Buy two cards for 4 disks.  Or a $300 server card for 8 disks.

> How does SATA fit in with all of this?  Is it basically the same
> limitations on the bus as IDE/PATA, so that you'd really not want to put
> more than 1 device per bus?

SATA mandates at most 1 disk per channel, making the issue moot.  It is
still true that there is only one active disk on a bus.  But then there
is only one disk on a bus.

-- 
	      Stuart D. Gathman <stuart@bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

  reply	other threads:[~2007-05-13  1:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12 21:42 [linux-lvm] LVM on SATA/PATA disks Bertrand Renuart
2007-05-13  1:12 ` Stuart D. Gathman
2007-05-13  1:23   ` Brian J. Murrell
2007-05-13  1:34     ` Stuart D. Gathman [this message]
2007-05-13  2:06       ` David Brown
2007-05-13 16:46         ` Les Mikesell
2007-05-13 17:24           ` Stuart D. Gathman
2007-05-14  8:38             ` Bryn M. Reeves
2007-05-14  8:30         ` Bryn M. Reeves
2007-05-14 15:24           ` David Brown
2007-05-15 14:35             ` Bryn M. Reeves
2007-05-13 20:25   ` Bertrand Renuart
2007-05-14 14:53     ` Stuart D. Gathman
2007-05-14 14:59     ` Daniel Davidson

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=Pine.LNX.4.44.0705122130070.27083-100000@bmsred.bmsi.com \
    --to=stuart@bmsi.com \
    --cc=linux-lvm@redhat.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).