From: John Quigley <jquigley@jquigley.com>
To: XFS Development <xfs@oss.sgi.com>
Subject: Best design docs for XFS
Date: Mon, 10 Aug 2009 16:23:19 -0500 [thread overview]
Message-ID: <4A808FC7.2020800@jquigley.com> (raw)
Hey Folks:
What are the best and most current technical design documents pertaining to (Linux port of) XFS, as a companion to reading the actual code? Based upon what I've read on the community site:
http://xfs.org/index.php/XFS_Papers_and_Documentation
the most thorough technical documentation of the system lives at:
http://oss.sgi.com/projects/xfs/design_docs/xfsdocs93_pdf/
My only concern with the above is the age - are these sufficiently up-to-date from an architecture perspective? Thanks very much.
- John Quigley
home: www.jquigley.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-08-10 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 21:23 John Quigley [this message]
2009-08-10 22:56 ` Best design docs for XFS Eric Sandeen
2009-08-11 2:53 ` Christoph Hellwig
2009-08-11 17:27 ` John Quigley
2009-08-11 17:47 ` Eric Sandeen
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=4A808FC7.2020800@jquigley.com \
--to=jquigley@jquigley.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