public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Andre Hedrick <andre@linux-ide.org>,
	Arjan van de Ven <arjan@fenrus.demon.nl>,
	Paul Flinders <P.Flinders@ftel.co.uk>,
	linux-kernel@vger.kernel.org, Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: Help with Fasttrack/100 Raid on Linux
Date: Thu, 19 Apr 2001 18:39:51 +0200	[thread overview]
Message-ID: <3ADF14D7.B1ADC8C2@gmx.at> (raw)
In-Reply-To: <Pine.LNX.4.10.10104171921300.23608-100000@master.linux-ide.org> <3ADDF370.FAEF5117@gmx.at>

Wilfried Weissmann wrote:
> 
> Andre Hedrick wrote:
> >
> > The really easy thing to do is to come up with the personality rules you
> > want to se and let me create the API.  I can make drives talk, listen,
> > dance, spin, flip, etc.....

[snip]

> Talking about the API... These should be the basic steps that we need to
> do (unordered, this is just brainstorming):
> 
> *) device_size_calculation() should use a callback of the raid level to
> get the device size. Or the code should be completly moved over to the
> <raid level>_run()'s.
> 
> *) Hide/unhide disks from the userland (this is just a cosmetic issue).
> 
> *) Shift sectors and shrink capacity of disks so that the existing raid
> levels can access the disks according to the ata-raid layout.
> 
> *) Get the configuration sector from disk. Analyse the configuration and
> setup disks and md-devices.
> 
> *) All raid pers. must be able to handle I/O that requests sectors from
> more than only one disk.
> 
> *) Partitioned raid devices must be handled somehow.

OK, partitions are already handeled!

One additional thing: I am thinking were to put the configuration
detection code. For now I will try to put it at the end of md_init().
But I still have to figure out how I can read the config sector and
start a new md.
An API interface for that would also be great! My solution can only be
an ugly work-around. md_init() just seems not to be the right function
for that.

regards,
Wilfried

PS: I do not want to flood lkml with my stuff. Should we discuss this in
private?

-- 
Wilfried Weissmann ( mailto:Wilfried.Weissmann@gmx.at )
Mobile: +43 676 9444465

  reply	other threads:[~2001-04-19 16:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3AD64568.28E170B6@mediaone.net>
2001-04-13  4:01 ` Help with Fasttrack/100 Raid on Linux Andre Hedrick
2001-04-13  8:09   ` Paul Flinders
2001-04-13 19:35     ` Arjan van de Ven
2001-04-13 22:15       ` Erik van Asselt
2001-04-16 20:33       ` Wilfried Weissmann
2001-04-16 20:51         ` Andre Hedrick
2001-04-17 12:14           ` Wilfried Weissmann
2001-04-18  2:44             ` Andre Hedrick
2001-04-18 20:05               ` Wilfried Weissmann
2001-04-19 16:39                 ` Wilfried Weissmann [this message]
2001-04-22  4:10                 ` Andre Hedrick
2001-04-25 15:10                   ` Wilfried Weissmann
     [not found] <3AD62556.7A35DF69@mediaone.net>
2001-04-12 22:34 ` Andre Hedrick
2001-04-13  0:14   ` Tim Moore
2001-04-13  0:26     ` Alan Cox

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=3ADF14D7.B1ADC8C2@gmx.at \
    --to=wilfried.weissmann@gmx.at \
    --cc=P.Flinders@ftel.co.uk \
    --cc=andre@linux-ide.org \
    --cc=arjan@fenrus.demon.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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