public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Cc: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>,
	Arjan van de Ven <arjanv@redhat.com>,
	"Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	Device mapper devel list <dm-devel@redhat.com>,
	Thomas Horsten <thomas@horsten.com>,
	medley@lists.infowares.com
Subject: Re: ATARAID/FakeRAID/HPTRAID/PDCRAID as dm targets?
Date: Mon, 22 Mar 2004 14:29:44 -0500	[thread overview]
Message-ID: <405F3EA8.6060606@pobox.com> (raw)
In-Reply-To: <405F3B1C.3030500@gmx.net>

Carl-Daniel Hailfinger wrote:
> Wilfried Weissmann wrote:
> 
>>Arjan van de Ven wrote:
>>
>>
>>>On Sat, Mar 20, 2004 at 07:23:01PM -0700, Kevin P. Fleming wrote:
>>>
>>>
>>>>Jeff Garzik wrote:
>>>>
>>>>
>>>>
>>>>>So go ahead, and I'll lend you as much help as I can.  I have the
>>>>>full Promise RAID docs, and it seems like another guy on the lists
>>>>>has full Silicon Image "medley" RAID docs...
> 
> 
> Jeff: May I request your docs?

Unfortunately not, but I can get you in touch with somebody at Promise 
who can.  They're definitely interested in working with the open source 
community.  Not public...


> Well, I had something in mind which closely resembles the ataraid-detect
> tool Thomas Horsten (Medley RAID) suggested.
> 
> http://lists.infowares.com/archive/medley/2004-February/000001.html
> 
> OK, I was even aiming for less: Write an ataraid-detect tool which outputs
> the correct mapping for dmsetup. If I manage to write it generically
> enough, it can be integrated into evms or used as a standalone program,
> whatever you like.

That's pretty nice.  Very Unix-ish:  provide a small, pluggable piece 
that does one thing, and does it well.


>>1. its all within evms
>>There is no need for additional tools required to setup the volume
>>(thinking about installers and initrd...).
> 
> 
> The EVMS sample initrd is HUGE. (2.1 MB) I'm aiming for a initrd size of
> less than 1/10 of that.

Cool :)


>>4. nice clickety-click user interface
>>Especially useful for lazy people like me. ;)
> 
> 
> I prefer the "no user interface" approach. But then again, I'm biased.

Agreed -- a minimal implementation is needed first anyway.  The BIOS of 
these proprietary RAID thingies typically provides the user interface.


>>What do you think?
> 
> 
> I'll use your work as a foundation. First step is integrating detection
> for non-HPT arrays. If the code looks too messy after that, I still can
> refactor it.
> 
> As soon as I have some code to get at least PDCRAID working, I'll post again.

Feel free to ask me questions, too.

	Jeff




  reply	other threads:[~2004-03-22 19:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-20 18:19 ATARAID/FakeRAID/HPTRAID/PDCRAID as dm targets? Carl-Daniel Hailfinger
2004-03-20 20:51 ` Jeff Garzik
2004-03-21  2:23   ` Kevin P. Fleming
2004-03-21  7:47     ` Arjan van de Ven
2004-03-21 13:47       ` Wilfried Weissmann
2004-03-22 19:14         ` Carl-Daniel Hailfinger
2004-03-22 19:29           ` Jeff Garzik [this message]
2004-03-23 21:15             ` Wilfried Weissmann
2004-04-01  3:06               ` Carl-Daniel Hailfinger
2004-04-01  3:19             ` Carl-Daniel Hailfinger
2004-04-01  5:28               ` Jeff Garzik
2004-03-23 21:03           ` Wilfried Weissmann
2004-03-21 18:07     ` Jeff Garzik
2004-03-21 18:40       ` Carl-Daniel Hailfinger
2004-03-21 18:45         ` Kevin P. Fleming
2004-03-21 19:44           ` Carl-Daniel Hailfinger
2004-03-21 20:01             ` Carl-Daniel Hailfinger
2004-03-21 20:19               ` christophe varoqui
2004-03-22 11:46                 ` Carl-Daniel Hailfinger
2004-03-21 18:58         ` Måns Rullgård
2004-03-24 18:21   ` Pedro Larroy

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=405F3EA8.6060606@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=Wilfried.Weissmann@gmx.at \
    --cc=arjanv@redhat.com \
    --cc=c-d.hailfinger.kernel.2004@gmx.net \
    --cc=dm-devel@redhat.com \
    --cc=kpfleming@backtobasicsmgmt.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=medley@lists.infowares.com \
    --cc=thomas@horsten.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