From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Saket Sinha <saket.sinha89@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
lsf-pc@lists.linux-foundation.org
Subject: Re: [LSF/MM ATTEND] Stackable Union Filesystem Implementation
Date: Wed, 08 Jan 2014 01:52:59 +0900 [thread overview]
Message-ID: <25625.1389113579@jrobl> (raw)
In-Reply-To: <CAK25hWOu-Q0H8_RCejDduuLCA1-135BEp_Cn_njurBA4r7zp5g@mail.gmail.com>
Saket Sinha:
> 1. VFS-based stacking solution- I would like to cite the work done by
> Valerie Aurora was closest.
>
> 2. Non-VFS-based stacking solution - UnionFS, Aufs and the new Overlay FS
Overayfs is essentially a rewrite of UnionMount (implemented in VFS
layer), to be a filesystem. They both have several unresolved issues by
design "name-based union", and I have pointed out on LKML several times.
For example, here is a URL of my last post about it.
http://marc.info/?l=linux-kernel&m=136310958022160&w=2
> The use case that I am looking from the stackable filesystem is that
> of "diskless node handling" (for CERN where it is required to provide
> a faster diskless
> booting to the Large Hadron Collider Beauty nodes).
Just out of curious, I remember a guy in CERN had posted a message to
aufs-users ML.
http://www.mail-archive.com/aufs-users@lists.sourceforge.net/msg04020.html
Are you co-working with him? Or CERN totally stopped using aufs?
J. R. Okajima
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-01-07 16:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 10:34 [LSF/MM ATTEND] Stackable Union Filesystem Implementation Saket Sinha
2014-01-07 12:23 ` Jan Kara
2014-01-07 20:04 ` Saket Sinha
2014-01-08 5:10 ` J. R. Okajima
2014-01-08 5:10 ` J. R. Okajima
2014-01-08 18:06 ` Saket Sinha
2014-01-09 7:32 ` J. R. Okajima
2014-01-09 7:32 ` J. R. Okajima
2014-01-09 9:19 ` Saket Sinha
2014-01-09 14:17 ` J. R. Okajima
2014-01-11 17:21 ` Saket Sinha
2014-01-08 11:16 ` Jan Kara
2014-01-08 11:16 ` Jan Kara
2014-01-08 18:26 ` Saket Sinha
2014-01-08 21:26 ` Jan Kara
2014-01-09 10:06 ` Saket Sinha
2014-01-07 16:52 ` J. R. Okajima [this message]
2014-01-07 20:21 ` Saket Sinha
-- strict thread matches above, loose matches on Subject: below --
2014-01-07 10:32 Saket Sinha
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=25625.1389113579@jrobl \
--to=hooanon05g@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=saket.sinha89@gmail.com \
/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.