From: Lachlan McIlroy <lachlan@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>, xfs-dev <xfs-dev@sgi.com>
Subject: Re: [patch] Fix broken inode clustering
Date: Fri, 09 Nov 2007 12:09:35 +1100 [thread overview]
Message-ID: <4733B34F.70407@sgi.com> (raw)
In-Reply-To: <20071108003848.GA66820511@sgi.com>
Looks good Dave.
David Chinner wrote:
> The radix tree based inode caches did away with the inode cluster hashes,
> replacing them with a bunch of masking and gang lookups on the radix tree.
>
> This masking got broken when moving the code to per-ag radix trees and
> indexing by agino # rather than straight inode number. The result is
> clustered inode writeback does not cluster and things can go extremely
> slowly when there are lots of inodes to write.
>
> The following patch fixes this up by comparing agino # of the inode
> found to the index of the cluster we are looking for.
>
> Signed-off-by: Dave Chinner <dgc@sgi.com>
> Tested-by: Torsten Kaiser <just.for.lkml@googlemail.com>
>
> ---
> fs/xfs/xfs_iget.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: 2.6.x-xfs-new/fs/xfs/xfs_iget.c
> ===================================================================
> --- 2.6.x-xfs-new.orig/fs/xfs/xfs_iget.c 2007-11-02 13:44:46.000000000 +1100
> +++ 2.6.x-xfs-new/fs/xfs/xfs_iget.c 2007-11-07 13:08:42.534440675 +1100
> @@ -248,7 +248,7 @@ finish_inode:
> icl = NULL;
> if (radix_tree_gang_lookup(&pag->pag_ici_root, (void**)&iq,
> first_index, 1)) {
> - if ((iq->i_ino & mask) == first_index)
> + if ((XFS_INO_TO_AGINO(mp, iq->i_ino) & mask) == first_index)
> icl = iq->i_cluster;
> }
>
>
>
>
prev parent reply other threads:[~2007-11-09 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 0:38 [patch] Fix broken inode clustering David Chinner
2007-11-09 1:09 ` Lachlan McIlroy [this message]
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=4733B34F.70407@sgi.com \
--to=lachlan@sgi.com \
--cc=dgc@sgi.com \
--cc=xfs-dev@sgi.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