public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Peter J. Braam" <braam@clusterfs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC] Lustre VFS patch, version 2
Date: Sun, 6 Jun 2004 18:00:01 +0100	[thread overview]
Message-ID: <20040606170001.GA10258@infradead.org> (raw)
In-Reply-To: <9025E129D3FCD340A7BA67E342D10E7AF11B72@proxy.mse1.mailstreet.com>

On Thu, Jun 03, 2004 at 11:53:43AM -0400, Peter J. Braam wrote:
> Perhaps it is useful to explain that vendors (Novell, Dell, HP and
> others) have urged me to enquire if the hooks could go into 2.6.  All of
> them have really major Lustre customers, running top10 super computing
> clusters with Lustre.  Having the hooks avoids having to patch vendor
> kernels, which breaks support arrangements.  As for our position, it's
> in fact easier to wait and just collect clever insights from time to
> time. 
> 
> I represent them here.  I understand and would respect the wait until
> 2.7 argument, but I think it is workable to get them into 2.6.  Is it
> really a big deal to go through these small patches a few more times to
> judge if they are safe, and to include them?  I think it would help
> people who care and support Linux financically.  I only hear Christoph
> arguing against it, are there other insights?

Trond also clearly spoke against it and Anton didn't seem to be impressed
by the code quality of your patches either ;-)  Only lmb who certainly
has a vested interest by beeing responsible for cluster at one of the above
mentioned vendors has speaken for it.  Given that SLES9 will already have
lustre life should already be much simpler for you.  If clusterfs is
actually interested in maintaining lustre as part of the linux kernel I'm
the last one to object, but without you place the burden of maintaining
all the hooks that are very specific to your filesystem on us.

p.s. where's lustre's current cvs tree?  I'd like to actually build a module
vs the hooks that you posted and growel in the cvs history a little. 

  reply	other threads:[~2004-06-06 17:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 15:53 [PATCH/RFC] Lustre VFS patch, version 2 Peter J. Braam
2004-06-06 17:00 ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-02 23:15 Peter J. Braam
2004-06-03 13:59 ` Christoph Hellwig
2004-06-03 14:19   ` Lars Marowsky-Bree
2004-06-03 14:26     ` Christoph Hellwig
2004-06-03 14:33     ` Christoph Hellwig
2004-06-03 14:49     ` Trond Myklebust
2004-06-03 18:10     ` Jan Harkes
2004-06-04  5:03     ` Daniel Phillips
2004-06-03 14:27 ` Christoph Hellwig
2004-06-04 16:55 ` Anton Blanchard
2004-06-07 18:02   ` Dipankar Sarma

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=20040606170001.GA10258@infradead.org \
    --to=hch@infradead.org \
    --cc=braam@clusterfs.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