All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. R. Okajima" <hooanon05@yahoo.co.jp>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: 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: Fri, 21 Sep 2012 06:30:41 +0900	[thread overview]
Message-ID: <32710.1348176641@jrobl> (raw)
In-Reply-To: <877grozaih.fsf@tucsk.pomaz.szeredi.hu>


Miklos Szeredi:
> 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(-)

Yes, I have to admit that aufs grew up very big.
The fundamental (by design) difference between them is considering how
important the filesystem semantics is. You may dislike a big module,
but I am interested in how you (or someone else) will implement the
missing overlayfs features to keep the semantics. One approach is
implemented in aufs. I guess you will try another one. That is what I am
interesed.


J. R. Okajima

  reply	other threads:[~2012-09-20 21:30 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 [this message]
2012-09-23 13:02     ` Jan Engelhardt

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=32710.1348176641@jrobl \
    --to=hooanon05@yahoo.co.jp \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=dhowells@redhat.com \
    --cc=ezk@fsl.cs.sunysb.edu \
    --cc=hch@infradead.org \
    --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 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.