From: David Nicol <davidnicol@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: a possible path to file system convergence
Date: Mon, 8 Feb 2010 15:46:13 -0600 [thread overview]
Message-ID: <934f64a21002081346y285f8ee7n3e7d9132e26d217b@mail.gmail.com> (raw)
when i first read about BTRFS i had a bunch of thoughts which
eventually produced a concept. That concept is, decoupling "extent
management" from other file system features. The resulting vision is a
situation in which persistent storage is obtained with a small suite
of extent allocation syscalls analogous to malloc and free, but
persistent, and these services are both provided and used by compliant
FSes, resulting in the ability to have one file system slosh around to
various spindles in various on-disk formats.
I don't plan on being in Boston in August but if I went that is what I
would try to present on.
--
Is it the time when there isn't time to discuss but there is time to act yet?
reply other threads:[~2010-02-08 21:46 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=934f64a21002081346y285f8ee7n3e7d9132e26d217b@mail.gmail.com \
--to=davidnicol@gmail.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).