public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [RFC 0/3] Future Directions for XFS....
Date: Tue, 23 Sep 2008 17:59:10 +1000	[thread overview]
Message-ID: <20080923075910.GA5448@disturbed> (raw)

Folks,

I'm about to post a set of three documents that I was in the process
of writing while working on contract for Agami Systems.  I have
managed to get them extracted from the corpse of Agami so that the
concepts and thoughts are not lost.

The documents encompass three different areas of interest - the
inode subsystem, journalling and reliability - and try to encompass
all the concepts and ideas that had either been used to solve
problems or were considered the way forward to solve further issues
that were being seen.

I'm hoping that these documents will go a long way to defining the
future direction and development plan for the XFS community.  At
minimum I am hoping that these documents will foster an amount of
discussion and provide tasks for anyone who wants to contribute to
XFS.

I intend to keep the documents up to date according to the
discussion that occurs so that they can form reference documentation
when it comes to implementing various features. Suggestions on the
best place to host these documents are welcome....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

             reply	other threads:[~2008-09-23  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23  7:59 Dave Chinner [this message]
2008-09-23  8:02 ` [RFC 1/3] Future Directions - Inode Subsystems Dave Chinner
2008-09-23  8:03 ` [RFC 2/3] Future Directions - Journalling Dave Chinner
2008-09-23  8:05 ` [RFC 3/3] Future Directions - Reliability Dave Chinner
2008-09-25  0:39   ` Christoph Hellwig

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=20080923075910.GA5448@disturbed \
    --to=david@fromorbit.com \
    --cc=xfs@oss.sgi.com \
    /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