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, trond.myklebust@fys.uio.no, anton@samba.org
Subject: Re: [PATCH/RFC] Lustre VFS patch, version 2
Date: Thu, 3 Jun 2004 15:33:38 +0100 [thread overview]
Message-ID: <20040603143338.GA16957@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:
> 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.
And btw, I didn't say from the beginning. I just want a comitment from
the lustre folks that they're merging it so we can work out the rough edges
together. There's not much of a problem doing the merge spread over a few
kernel releases.
> Lustre alone would be, roughly, ~10MB more sources, just in the kernel.
I think for mainline mostly the client, aka the llite directory would
be interesting, so a linux box can simply join the lustre cluster. the
metadata server and even worse the object storage box mods would require
tons of work to get anywhere a mergeable shape and are less interesting
anyway.
next prev parent 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
2004-06-03 14:33 ` Christoph Hellwig [this message]
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=20040603143338.GA16957@infradead.org \
--to=hch@infradead.org \
--cc=anton@samba.org \
--cc=arjanv@redhat.com \
--cc=axboe@suse.de \
--cc=braam@clusterfs.com \
--cc=kevcorry@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--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