linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Saket Sinha <saket.sinha89@gmail.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org
Subject: [LSF/MM ATTEND] Stackable Union Filesystem Implementation
Date: Tue, 7 Jan 2014 16:04:03 +0530	[thread overview]
Message-ID: <CAK25hWOu-Q0H8_RCejDduuLCA1-135BEp_Cn_njurBA4r7zp5g@mail.gmail.com> (raw)

I would like to attend LSF/MM summit. I will like to discuss approach
to be taken to finally bring up a Union Filesystem for Linux kernel.

My tryst with Union Filesystem began when I was involved developing a
filesystem as a part of  GSOC2013(Google Summer of Code) for CERN
called Hepunion Filesystem.

CERN needs a union filesystem for LHCb to provide fast diskless
booting for its nodes. For such an implementation, they need a file
system with two branches a Read-Write and a Read Only so they decided
to write a completely new union file system called Hepunion. The
driver was  partially completed and worked somewhat with some issues
on 2.6.18. since they were using SCL5(Scientific Linux),

Now since LHCb is  moving to newer kernels, we ported it to newer
kernels but this is where the problem started. The design of our
filesystem was this that we used "path" to map the VFS and the lower
filesystems. With the addition of RCU-lookup in 2.6.35, a lot of
locking was added  in kernel functions like kern_path and made our
driver unstable beyond repair.

So now we are redesigning the entire thing from scratch.

We want to develop this Filesystem to finally have a stackable union
filesystem for the mainline Linux kernel . For such an effort,
collaborative development and community support is a must.


For the redesign, AFAIK
I can think of two ways to do it-

 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

Patches for kernel exists for overlayfs & unionfs.
What is  communities view like which one would be good fit to go with?

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).

 For this we need a
1. A global Read Only FIlesystem
2. A client-specific Read Write FIlesystem via NFS
3. A local Merged(of the above two) Read Write FIlesystem on ramdisk.

Thus to design such a fileystem I need community support and hence
want to attend LSF/MM summit.

  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>

             reply	other threads:[~2014-01-07 10:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 10:34 Saket Sinha [this message]
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
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=CAK25hWOu-Q0H8_RCejDduuLCA1-135BEp_Cn_njurBA4r7zp5g@mail.gmail.com \
    --to=saket.sinha89@gmail.com \
    --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