From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/6] XFS: replace the mount inode list with radix tree traversals
Date: Wed, 8 Oct 2008 08:41:26 +1100 [thread overview]
Message-ID: <1223415692-6354-1-git-send-email-david@fromorbit.com> (raw)
The list of all inodes on a mount is superfluous. We can traverse
all inodes now by walking the per-AG inode radix trees without
needing a separate list. This enables us to remove a bunch of
complex list traversal code and remove another two pointers from
the xfs_inode.
Also, by replacing the sync traversal with an ascending inode
number traversal, we will issue better inode I/O patterns for
writeback triggered by xfssyncd or unmount.
Before we make this change, move all the relevant sync code
into it's own file in the linux-2.6/ directory. This aggregates
VFS specific sync interfacing in the one file and will allow
all the subsequent change history to be associated with this
file so it is easy to find in future.
next reply other threads:[~2008-10-07 21:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 21:41 Dave Chinner [this message]
2008-10-07 21:41 ` [PATCH 1/6] XFS: move sync code to its own file Dave Chinner
2008-10-07 21:41 ` [PATCH 2/6] XFS: move xfssyncd code to xfs_sync.c Dave Chinner
2008-10-07 21:41 ` [PATCH 3/6] XFS: Remove xfs_iflush_all and clean up xfs_finish_reclaim_all() V3 Dave Chinner
2008-10-07 21:41 ` [PATCH 4/6] XFS: Use the inode tree for finding dirty inodes V3 Dave Chinner
2008-10-07 21:41 ` [PATCH 5/6] XFS: Traverse inode trees when releasing dquots V3 Dave Chinner
2008-10-07 21:41 ` [PATCH 6/6] XFS: remove the mount inode list Dave Chinner
2008-10-08 18:20 ` [PATCH 0/6] XFS: replace the mount inode list with radix tree traversals Christoph Hellwig
2008-10-08 23:59 ` Dave Chinner
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=1223415692-6354-1-git-send-email-david@fromorbit.com \
--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