linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "Justin T. Gibbs" <Justin_Gibbs@adaptec.com>,
	linux-raid@vger.kernel.org,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: "Enhanced" MD code avaible for review]
Date: Wed, 17 Mar 2004 14:28:59 -0500	[thread overview]
Message-ID: <4058A6FB.6080602@pobox.com> (raw)
In-Reply-To: <20040317190916.GA24118@lst.de>


(added linux-kernel to CC, where IMO the discussion on wider issues belongs)

Christoph Hellwig wrote:
> On Wed, Mar 17, 2004 at 12:05:51PM -0700, Justin T. Gibbs wrote:
>>I'm aware of Neil's past comments on the subject, but I was not aware
>>of a more full discussion on what this means in terms of lost functionality
>>for Linux.  I would like to have that discussion.  I'm more than willing
>>to adjust our strategy once that discussion takes place and a consensus
>>is reached.
> 
> 
> We're not far enough to actually removing functionlly yet.  For that
> early userspace needs to get a little more mature and more widely used.
> 
> We're not going to add more functionaly like that. though.

If early userspace isn't ready, it sounds like a choice between 
"nothing" and "it works".

We want a clean, tasteful solution, sure.  But I think we can work 
within the confines of the existing 2.6 API, and not postpone this stuff 
under early userspace is ready.

<rant>
Overall... the storage industry finally got off their ass and created a 
vendor-neutral RAID format, and they're actually using it.  Linux users 
don't deserve to be left out in the cold until 2.7.x klibc stuff is in, 
since they will be buying such RAID hardware right now.

I got into the Linux kernel game years ago in a large part because of 
precisely this -- getting Linux users going on hardware that would 
otherwise be Windows-only, without my help.  (or would otherwise be a 
grotty and buggy vendor driver, without my help:))
</rant>

	Jeff




  reply	other threads:[~2004-03-17 19:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <405899E8.8070806@pobox.com>
2004-03-17 18:37 ` [Fwd: "Enhanced" MD code avaible for review] Christoph Hellwig
2004-03-17 18:54   ` Justin T. Gibbs
2004-03-17 19:01     ` Christoph Hellwig
2004-03-17 19:05       ` Justin T. Gibbs
2004-03-17 19:09         ` Christoph Hellwig
2004-03-17 19:28           ` Jeff Garzik [this message]
2004-03-17 19:34             ` Christoph Hellwig
2004-03-17 19:41               ` Jeff Garzik
2004-03-17 19:23       ` Hendrik Visage

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=4058A6FB.6080602@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=Justin_Gibbs@adaptec.com \
    --cc=hch@lst.de \
    --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;
as well as URLs for NNTP newsgroup(s).