From: Saket Sinha <saket.sinha89@gmail.com>
To: "J. R. Okajima" <hooanon05g@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
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: Sat, 11 Jan 2014 22:51:52 +0530 [thread overview]
Message-ID: <CAK25hWPpgShw_mWcqWrwGifMXdvF4qDyNojsBAA-si6KPNX68A@mail.gmail.com> (raw)
In-Reply-To: <8411.1389277071@jrobl>
> Currently it is unclear which evolution way hepunion will take, but if
> you want
> - filesystem-type union (instead of mount-type union nor block device
> level union)
> - and name-based union (insated of inode-based union)
> then the approach is similar to overlayfs's.
> So it might be better to make overlayfs as the base of your development.
> If supporting NFS branch (or exporting hepunion) is important for you,
> then the inode-based solution will be necessary.
>
Thanks for the suggestion. I am looking forward to suggestions like
these from the community so that we can have a universal union
filesystem for mainline linux kernel with most of the use
cases(including Cern's).
Regards,
Saket Sinha
--
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-11 17:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 10:34 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 18:06 ` Saket Sinha
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 [this message]
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
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=CAK25hWPpgShw_mWcqWrwGifMXdvF4qDyNojsBAA-si6KPNX68A@mail.gmail.com \
--to=saket.sinha89@gmail.com \
--cc=hooanon05g@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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