mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Saout <christophe@saout.de>
To: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: ATARAID userspace configuration tool
Date: Wed, 11 Feb 2004 12:34:19 +0100	[thread overview]
Message-ID: <1076499258.5253.1.camel@leto.cs.pocnet.net> (raw)
In-Reply-To: <4029892C.2070009@backtobasicsmgmt.com>

Am Mi, den 11.02.2004 schrieb Kevin P. Fleming um 02:45:

> The tricky part is for Thomas' ataraid-detect program to keep some 
> information around when it has seen the first component of a RAID-0 but 
> not the second (or vice-versa). It would be very inefficient to scan all 
> known block devices every time a new one is added, although that 
> brute-force method could be used just to get the program working at 
> first. Once the whole idea has been tested and works properly (the 
> ATARAID devices become available and function properly), the efficiency 
> problem(s) could be addressed.

Aren't the disks the ATARAID is made of usually on the same controller?
Then you only have to scan that one.



  reply	other threads:[~2004-02-11 11:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10 14:18 Thomas Horsten
2004-02-10 14:51 ` Matt Domsch
2004-02-10 14:58 ` Christophe Saout
2004-02-10 18:26   ` Kevin P. Fleming
2004-02-10 19:18     ` Christophe Saout
2004-02-10 19:24       ` Kevin P. Fleming
2004-02-11  1:35       ` Greg KH
2004-02-11  1:45         ` Kevin P. Fleming
2004-02-11 11:34           ` Christophe Saout [this message]
2004-02-11 14:18             ` Kevin P. Fleming
2004-02-11 19:48               ` Christophe Saout
2004-02-10 17:38 ` Jeff Garzik
2004-02-10 17:47   ` Thomas Horsten
2004-02-10 18:44     ` Jeff Garzik
2004-02-10 22:41 ` Neil Brown

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=1076499258.5253.1.camel@leto.cs.pocnet.net \
    --to=christophe@saout.de \
    --cc=kpfleming@backtobasicsmgmt.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®