Linux filesystem development
 help / color / mirror / Atom feed
From: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Al Boldi <a1426z@gawab.com>,
	Eric Van Hensbergen <ericvh@gmail.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] VFS: FS CoW using redirection
Date: Sun, 27 Aug 2006 22:10:57 -0400	[thread overview]
Message-ID: <20060828021057.GA30334@filer.fsl.cs.sunysb.edu> (raw)
In-Reply-To: <20060827171510.GA3502@wohnheim.fh-wedel.de>

On Sun, Aug 27, 2006 at 07:15:10PM +0200, Jörn Engel wrote:
> On Sat, 26 August 2006 22:05:21 +0300, Al Boldi wrote:
... 
> > > Or you can give Unionfs a try: http://www.unionfs.org
> > 
> > UnionFS is great, but it incurs additional overhead, as it lives below the 
> > real VFS.  What could be really great, is to move some basic functionality 
> > abstractions from UnionFS into VFS proper.
> 
> If you want to make this vision happen, one of the missing pieces is a
> method for copyup, an in-kernel copying routine.  Unionfs needs is
> just the same as Jan's patches do and in the past Linus didn't like my
> approach of using sendfile for it.  You could take a stab at the
> splice code and see how that can be used for copyup.

The thing with union mounts/unionfs is that some of the functionality makes
sense to have in a file system while other parts make sense to have in the
VFS - the way I see it, namespace related bits should be in VFS while
persistent state should be done on the file system level.

Josef "Jeff" Sipek.

-- 
If I have trouble installing Linux, something is wrong. Very wrong.
		- Linus Torvalds
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2006-08-28  2:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-08 17:41 [RFC] VFS: FS CoW using redirection Al Boldi
2006-07-08 18:32 ` Eric Van Hensbergen
2006-07-09 12:50   ` Al Boldi
2006-07-11 19:57     ` Al Boldi
2006-08-23 17:24     ` Jörn Engel
2006-08-23 18:05       ` Josef Sipek
2006-08-26 19:05         ` Al Boldi
2006-08-27 17:15           ` Jörn Engel
2006-08-28  2:10             ` Josef Sipek [this message]
2006-07-09  2:53 ` Shaya Potter

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=20060828021057.GA30334@filer.fsl.cs.sunysb.edu \
    --to=jsipek@fsl.cs.sunysb.edu \
    --cc=a1426z@gawab.com \
    --cc=ericvh@gmail.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --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