public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	"Peter J. Braam" <braam@clusterfs.com>,
	linux-kernel@vger.kernel.org, axboe@suse.de, kevcorry@us.ibm.com,
	arjanv@redhat.com, iro@parcelfarce.linux.theplanet.co.uk,
	trond.myklebust@fys.uio.no, anton@samba.org,
	lustre-devel@clusterfs.com
Subject: Re: [PATCH/RFC] Lustre VFS patch, version 2
Date: Thu, 3 Jun 2004 15:26:40 +0100	[thread overview]
Message-ID: <20040603142640.GA16837@infradead.org> (raw)
In-Reply-To: <20040603141922.GI4423@marowsky-bree.de>

On Thu, Jun 03, 2004 at 04:19:22PM +0200, Lars Marowsky-Bree wrote:
> On 2004-06-03T14:59:52,
>    Christoph Hellwig <hch@infradead.org> said:
> 
> > > Well, how close are we now to this being acceptable?
> > As already mentioned above they're completely uninteresting without
> > actually getting the user in tree _and_ maintained there (unlike e.g.
> > intermezzo or coda that are creeping along).  I think based on those
> > patch we should be able to properly integrate intermezzo once 2.7 opens.
> 
> This is something I've got to disagree with.
> 
> First, Inter-mezzo is reasonably dead, from what I can see. As is Coda.
> You'll notice that the developers behind them have sort-of moved on to
> Lustre ;-)

Arggg, sorry.  Typo there.  It should have of course read

"I think based on those patches we should be able to properly integrate
LUSTRE once 2.7 opens"

.oO(/me looks for a brown paperbag to hide)

> The logic that _all_ modules and functionality need to be "in the tree"
> right from the start for hooks to be useful is flawed, I'm afraid. Pure
> horror that a proprietary cluster file system might also profit from it
> is not, exactly, a sound technical argument. (I can assure you I don't
> care at all for the proprietary cluster-fs.)

It's more about maintaince overhead.   Maintaining features without the
user direct at hand isn't going anywhere.  Especially when messing around
deeply in the VFS.  By your argumentation we should also throw in all the
mosix and openssi hooks because they could be possibly useful, no? ;-)

> Another example of this is the cache invalidation hook which we went
> through a few weeks ago too. Back then you complained about not having
> an Open Source user (because it was requested by IBM GPFS), and so
> GFS/OpenGFS chimed in - now it is the lack of an _in-tree_ Open Source
> user...

I was always arguing against the lack of an intree user mostly.  Lack of
something that could we could merge even in the future is even worse.


  reply	other threads:[~2004-06-03 14:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02 23:15 [PATCH/RFC] Lustre VFS patch, version 2 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2004-06-03 15:53 Peter J. Braam
2004-06-06 17:00 ` Christoph Hellwig

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=20040603142640.GA16837@infradead.org \
    --to=hch@infradead.org \
    --cc=anton@samba.org \
    --cc=arjanv@redhat.com \
    --cc=axboe@suse.de \
    --cc=braam@clusterfs.com \
    --cc=iro@parcelfarce.linux.theplanet.co.uk \
    --cc=kevcorry@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmb@suse.de \
    --cc=lustre-devel@clusterfs.com \
    --cc=trond.myklebust@fys.uio.no \
    /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