Greetings... Thanks for the encouraging words <g>... We're getting the text together for a [PATCH 0/4] and also a patch for Documentation/filesystems/orangefs.txt. I have submitted a patch to fix the Kconfig default=y problem. I failed to cause patches 2/4, 3/4 and 4/4 to be emailed as replies to patch 1/4, and even though I included the right message-id on the --in-reply-to argument when I submitted the Kconfig patch with git-send-email, it doesn't seem threaded properly either... ? -Mike On Thu, Jan 1, 2015 at 12:48 PM, Boaz Harrosh <ooo@xxxxxxxxxxxxxxx> wrote: > On 12/31/2014 10:50 PM, hubcap wrote: >> From: Mike Marshall <hubcap@xxxxxxxxxxxx> >> >> This patch was built against v3.19-rc2, and is broken into four >> parts so that each part will be under the 100k linux-fsdevel limit. >> >> OrangeFS (formerly PVFS) is an lgpl licensed userspace networked parallel >> file system. OrangeFS can be accessed through included system utilities, >> user integration libraries, MPI-IO and can be used by the Hadoop >> ecosystem as an alternative to the HDFS filesystem. OrangeFS is used >> widely for parallel science, data analytics and engineering applications. >> >> While applications often don't require Orangefs to be mounted into >> the VFS, users do like to be able to access their files in the normal way. >> The Orangefs kernel client allows Orangefs filesystems to be mounted as >> a VFS. The kernel client communicates with a userspace daemon which in >> turn communicates with the Orangefs server daemons that implement the >> filesystem. The server daemons (there's almost always more than one) >> need not be running on the same host as the kernel client. >> >> Orangefs filesystems can also be mounted with FUSE, and we >> ship code and instructions to facilitate that, but most of our users >> report preferring to use our kernel module instead. Further, as an example >> of a problem we can't solve with fuse, we have in the works a >> not-yet-ready-for-prime-time version of a file_operations lock function >> that accounts for the server daemons being distributed across more >> than one running kernel. >> >> Many people and organizations, including Clemson University, >> Argonne National Laboratories and Acxiom Corporation have >> helped to create what has become Orangefs over more than twenty >> years. Some of the more recent contributors to the kernel client >> include: >> >> Christoph Hellwig >> Mike Marshall >> Randy Martin >> Becky Ligon >> Walt Ligon >> Michael Moore >> Rob Ross >> Phil Carnes >> >> Signed-off-by: Mike Marshall <hubcap@xxxxxxxxxxxx> >> --- >> fs/orangefs/downcall.h | 144 +++++++ >> fs/orangefs/protocol.h | 644 +++++++++++++++++++++++++++++++ >> fs/orangefs/pvfs2-bufmap.h | 76 ++++ >> fs/orangefs/pvfs2-debug.h | 276 ++++++++++++++ >> fs/orangefs/pvfs2-dev-proto.h | 101 +++++ >> fs/orangefs/pvfs2-kernel.h | 857 ++++++++++++++++++++++++++++++++++++++++++ >> fs/orangefs/pvfs2-proc.h | 16 + >> fs/orangefs/upcall.h | 251 +++++++++++++ > > Hi Mike > > Congratulation to all the Omnibond good folks and the OrangeFS community of users > and Developers! Good Job > > It is about time that we have this client for submission to the Kernel. I wish > you guys a smooth and fun ride in. > > I intend to give this and hard drive and review, but before I do this. > > I'm missing from this patchset (this patch and the other 4) a > Documentation/filesystems/orangefs.txt > > Documentation should include, among others, all needed Web URLS we need > to fetch and Install a working system. A brief of the installation > process. Farther reading, as well as as some 10 miles overview, philosophy > of operation, basic structure ... Anything interesting to a Kernel > developer ... > > I know that OrangeFS has excellent Documentation, it should be easy to > collect some of the highlights into this Doc. Please see in above > directory the Documentation of other FSs, for an example of scope > and general interests. Your call what you want to put in there, my > personal taste is: the more the better. > > One thing I would like to see in the [PATCH 0/4] (BTW please > submit as a patchset with a Title [PATCH 0/X] email), A bit more detail > about why OrangeFS is so nice, like Giga+ distributed Meta-Data, > redundancy, scalability, layouts, GUI ... the works. A short sales pitch that > will get us ordering two please. > > Thanks Mike > Boaz > -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
