linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Horsten <thomas@horsten.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] (2.4.2x) Driver for Medley software RAID (Silicon Image 3112 SATARaid, CMD680, etc?) for testing
Date: Mon, 4 Aug 2003 14:28:10 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.40.0308041418070.22732-100000@jehova.dsm.dk> (raw)
In-Reply-To: <1059995461.5291.0.camel@laptop.fenrus.com>

On 4 Aug 2003, Arjan van de Ven wrote:

> > I was under the impression that silraid.c never worked at all (it
> > certainly didn't on my system), because the magic number it looks for is
> > incorrect (actually, part of the drive's serial number), and thus not
> > present on all systems with this RAID).
>
> well... that's a 1 line fix to silraid.c......

Not really, it needs to look up the PCI device ID of the card to do it (of
course still just a few lines).

But the reason for rewriting the driver was that I wanted to use the
specification as a guideline instead of the old implementation which was
really for a different RAID type (with the cutoff handling of the
differing disk sizes etc).

In hindsight, after the driver is "completed" at least for RAID0, I can
see that modifying the old driver could have been just as good (although
I'd still advocate renaming it), but now it is done like this and I think
the new driver is certainly a better starting point for Medley (e.g. if
one wanted to add support for the striped modes etc).

Keep in mind that I didn't know anyone had successfully used silraid.c
since on my system it a) looked in the wrong place for the superblock and
b) looked for a wrong magic number, and I didn't get any response when I
provided you with a lot of details about this.

The detection of the arrays is certainly safer, and the make request
routine is improved in my driver so bottom line I thik it's a better
driver and will also provide a better starting point for adding stuff like
RAID1 and RAID0+1 support (although one could argue that the whole ataraid
method should be regarded as a temporary solution and there would be ways
to integrate support for these software RAIDs better in the future).

Regards,
Thomas



  reply	other threads:[~2003-08-04 12:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3F2BD6E2.9070101@pobox.com>
2003-08-04 10:49 ` [PATCH] (2.4.2x) Driver for Medley software RAID (Silicon Image 3112 SATARaid, CMD680, etc?) for testing Thomas Horsten
2003-08-04 11:11   ` Arjan van de Ven
2003-08-04 12:28     ` Thomas Horsten [this message]
     [not found] <Pine.LNX.4.40.0308012209180.29551-100000@jehova.dsm.dk>
2003-08-01 20:27 ` Arjan van de Ven
2003-08-01 20:25 Thomas Horsten
2003-08-02 12:59 ` Thomas Horsten

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.40.0308041418070.22732-100000@jehova.dsm.dk \
    --to=thomas@horsten.com \
    --cc=arjanv@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).