linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zach Brown <zach.brown@oracle.com>
To: linux-fsdevel@vger.kernel.org
Subject: CRFS source and project resources are now available
Date: Tue, 11 Mar 2008 18:17:31 -0700	[thread overview]
Message-ID: <47D72F2B.2010700@oracle.com> (raw)

Hello everyone,

Back at this year's LCA I gave a talk introducing CRFS, a cache coherent
networked file system.

  http://linux.conf.au/programme/detail?TalkID=247
  http://mirror.linux.org.au/pub/linux.conf.au/2008/Fri/mel8-247.ogg

At the time of the talk the source wasn't available.  It's now available
in a mercurial repository, along with the usual set of mailing lists, at:

  http://oss.oracle.com/projects/crfs/

The project is still early alpha which is why I'm only sending this
initial mail to -fsdevel.  In the coming months it should stabilize and
be more suitable for wider experimentation.  Now is the time to get
involved if you want to get your hands dirty in the initial design and
implementation.

I think the video recording of the talk does a decent job of giving an
overview of the design, and it's a hoot, but I can give a quick summary:

 - the user space server exports a private BTRFS volume
 - the network protocol operates on ranges of BTRFS disk items
 - the kernel client provides posix semantics by operating on items
 - the server can grant and revoke client caches of data and metadata

There's a lot of complexity hiding in those four lines but those are the
critical properties to grasp :).

The implementation has barely covered communicating item ranges between
the server and the client.  A single client can perform simple metadata
and data read and write operations.  Anything more complicated falls
over pretty quickly.  It's enough scaffolding to support divergent
concurrent development, though.

So, if this stuff interests you, do give it a try or share your thoughts
over on the crfs- mailing lists.

- z

                 reply	other threads:[~2008-03-12  1:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47D72F2B.2010700@oracle.com \
    --to=zach.brown@oracle.com \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).