linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@inai.de>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: "J. R. Okajima" <hooanon05@yahoo.co.jp>,
	viro@ZenIV.linux.org.uk, torvalds@linux-foundation.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	hch@infradead.org, akpm@linux-foundation.org, apw@canonical.com,
	nbd@openwrt.org, neilb@suse.de, jordipujolp@gmail.com,
	ezk@fsl.cs.sunysb.edu, dhowells@redhat.com,
	sedat.dilek@googlemail.com
Subject: Re: [PATCH 00/13] overlay filesystem: request for inclusion (v15)
Date: Sun, 23 Sep 2012 15:02:30 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.01.1209231500400.15692@nerf07.vanv.qr> (raw)
In-Reply-To: <877grozaih.fsf@tucsk.pomaz.szeredi.hu>


On Thursday 2012-09-20 22:48, Miklos Szeredi wrote:
>
>> Miklos, how do you think about this?
>> <http://marc.info/?l=linux-kernel&m=123938533724484&w=2>
>> Do you think UnionMount is totally gone?
>
>Unionmount provides almost the same functionality as overlayfs.  The big
>difference between the two is that unionmounts resides 100% in the VFS
>while 95% of overlayfs is plain filesystem code.  I think that's the
>biggest advantage: filesystem code is easier to maintain, has less
>impact on core complexity, etc.

The big advantage is actually that the unioned view is in a separate
namespace (vfsmount).

>Aufs provides much better filesystem semantics than either unionmounts
>or overlayfs.  But that does come at a price:
>
>aufs:       98 files changed, 29893 insertions(+), 7 deletions(-)
>overlayfs:  22 files changed, 2981 insertions(+), 10 deletions(-)

In two years time when sufficient user requests have come in,
overlayfs is likely to have wrong as much.

      parent reply	other threads:[~2012-09-23 13:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 18:55 [PATCH 00/13] overlay filesystem: request for inclusion (v15) Miklos Szeredi
2012-09-20 18:55 ` [PATCH 01/13] vfs: add i_op->dentry_open() Miklos Szeredi
2012-09-20 18:55 ` [PATCH 02/13] vfs: export do_splice_direct() to modules Miklos Szeredi
2012-09-20 18:55 ` [PATCH 03/13] vfs: introduce clone_private_mount() Miklos Szeredi
2012-09-20 18:55 ` [PATCH 04/13] overlay filesystem Miklos Szeredi
2012-09-20 18:55 ` [PATCH 05/13] overlayfs: add statfs support Miklos Szeredi
2012-09-20 18:55 ` [PATCH 06/13] overlayfs: implement show_options Miklos Szeredi
2012-09-20 18:55 ` [PATCH 07/13] overlay: overlay filesystem documentation Miklos Szeredi
2012-09-20 18:55 ` [PATCH 08/13] fs: limit filesystem stacking depth Miklos Szeredi
2012-09-20 18:55 ` [PATCH 09/13] overlayfs: fix possible leak in ovl_new_inode Miklos Szeredi
2012-09-20 18:55 ` [PATCH 10/13] overlayfs: create new inode in ovl_link Miklos Szeredi
2012-09-20 18:55 ` [PATCH 11/13] vfs: export __inode_permission() to modules Miklos Szeredi
2012-09-20 18:55 ` [PATCH 12/13] ovl: switch to __inode_permission() Miklos Szeredi
2012-09-20 18:55 ` [PATCH 13/13] overlayfs: copy up i_uid/i_gid from the underlying inode Miklos Szeredi
2012-09-20 19:34 ` [PATCH 00/13] overlay filesystem: request for inclusion (v15) J. R. Okajima
2012-09-20 20:48   ` Miklos Szeredi
2012-09-20 21:30     ` J. R. Okajima
2012-09-23 13:02     ` Jan Engelhardt [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=alpine.LNX.2.01.1209231500400.15692@nerf07.vanv.qr \
    --to=jengelh@inai.de \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=dhowells@redhat.com \
    --cc=ezk@fsl.cs.sunysb.edu \
    --cc=hch@infradead.org \
    --cc=hooanon05@yahoo.co.jp \
    --cc=jordipujolp@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=nbd@openwrt.org \
    --cc=neilb@suse.de \
    --cc=sedat.dilek@googlemail.com \
    --cc=torvalds@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).