> Sorry for the late reply. I was busy with some unavoidable circumstances.
I will come straight to my Filesystem project, this is a stackable filesystem I am developing for *CERN( the European Organization for Nuclear Research). *CERN needs a union filesystem for LHCb(Large Hadron Collider Beauty) to provide fast diskless booting for LHCb's 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. I would also like you to know that a proper Union filesystem has not been implemented for Linux kernel even after 20 years of its existence whereas Unix, BSD, Plan9 etc. have it from its earliest versions, though patches for UnionFS, Aufs and the new OverlayFS exist outside the mainline kernel. Now at CERN, the driver was written on a 2.6.18 kernel since they were using SCL5(Scientific Linux), the driver was partially completed. I was involved in this filesystem project as a part of GSOC2013(Google Summer of Code) where I ported the driver to 3.8 but this is where the problem started. The design of our filesystem was this that we used "path"(a VFS object) 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 I have a task where I have redesign it from scratch. My final objective is to code this filesystem driver to finally finish this Union filesystem issue for the Linux kernel, for the community and get it added to mainline kernel. Regards, Saket Sinha -- -- Mailing list guidelines and other related articles: http://lug-iitd.org/Footer --- You received this message because you are subscribed to the Google Groups "Linux User Group @ IIT Delhi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
