From: Ian Kent <raven@themaw.net>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, jblunck@suse.de,
dlezcano@fr.ibm.com, linux-kernel@vger.kernel.org,
bharata@linux.vnet.ibm.com, viro@ZenIV.linux.org.uk,
vaurora@redhat.com
Subject: Re: [rfc git patch] union directory
Date: Mon, 22 Dec 2008 23:22:59 +0900 [thread overview]
Message-ID: <1229955779.3040.2.camel@zeus.themaw.net> (raw)
In-Reply-To: <E1LElCn-0005gp-G1@pomaz-ex.szeredi.hu>
On Mon, 2008-12-22 at 14:52 +0100, Miklos Szeredi wrote:
>
> > Valerie Henson is planning to start a project (when she is done with
> > current commitments) along the lines of a lightweight stacking layer
> > with union support included in the file system. These continuing
> > individual efforts are a little disjoint so such a project could be an
> > ideal way to define what's needed, what the issues are and how it will
> > be done in one place. Hopefully everyone that is keen to see progress in
> > this area will want to be involved too, ;)
>
> Interesting.
>
> It maybe worth mentioning here that fuse is also a very capable
> "stacking layer" and with planned performance improvements it might
> become the best option to implement such fs stacks.
Yes, also an interesting thought.
How would you see fuse fitting into the overall solution of this problem
(aka what bits would live in the VFS and what bits would fuse address)?
Ian
prev parent reply other threads:[~2008-12-22 14:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 11:01 [rfc git patch] union directory Miklos Szeredi
2008-11-28 16:19 ` Bharata B Rao
2008-11-29 16:33 ` Miklos Szeredi
2008-12-01 3:57 ` hooanon05
2008-12-01 4:35 ` Bharata B Rao
2008-12-01 7:59 ` Bharata B Rao
2008-12-01 19:31 ` Miklos Szeredi
2008-12-01 16:24 ` David P. Quigley
2008-12-01 16:54 ` Erez Zadok
2008-12-17 5:21 ` Ian Kent
2008-12-18 16:45 ` Miklos Szeredi
2008-12-19 1:47 ` Ian Kent
2008-12-22 13:52 ` Miklos Szeredi
2008-12-22 14:22 ` Ian Kent [this message]
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=1229955779.3040.2.camel@zeus.themaw.net \
--to=raven@themaw.net \
--cc=bharata@linux.vnet.ibm.com \
--cc=dlezcano@fr.ibm.com \
--cc=jblunck@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=vaurora@redhat.com \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.