public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: John Quigley <jquigley@jquigley.com>
Cc: XFS Development <xfs@oss.sgi.com>
Subject: Re: Best design docs for XFS
Date: Mon, 10 Aug 2009 17:56:23 -0500	[thread overview]
Message-ID: <4A80A597.6050806@sandeen.net> (raw)
In-Reply-To: <4A808FC7.2020800@jquigley.com>

John Quigley wrote:
> 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.

It's pretty good still, the fundamental design is not substantially
changed; you're more likely to find missing bits than "wrong" bits I think.

http://oss.sgi.com/projects/xfs/training/index.html

has more info as well.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-08-10 22:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 21:23 Best design docs for XFS John Quigley
2009-08-10 22:56 ` Eric Sandeen [this message]
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=4A80A597.6050806@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=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