public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Alex Elder <aelder@sgi.com>,
	xfs@oss.sgi.com, John Hawley <warthog9@kernel.org>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [patch] xfs: properly account for reclaimed inodes
Date: Mon, 4 Oct 2010 12:22:13 +0200	[thread overview]
Message-ID: <20101004102213.GJ2618@cmpxchg.org> (raw)
In-Reply-To: <20101004071904.GH4681@dastard>

Hi,

On Mon, Oct 04, 2010 at 06:19:04PM +1100, Dave Chinner wrote:
> On Fri, Oct 01, 2010 at 12:17:23PM -0500, Alex Elder wrote:
> > On Fri, 2010-10-01 at 09:43 +0200, Johannes Weiner wrote:
> > > When marking an inode reclaimable, a per-AG counter is increased, the
> > > inode is tagged reclaimable in its per-AG tree, and, when this is the
> > > first reclaimable inode in the AG, the AG entry in the per-mount tree
> > > is also tagged.
> > > 
> > > When an inode is finally reclaimed, however, it is only deleted from
> > > the per-AG tree.  Neither the counter is decreased, nor is the parent
> > > tree's AG entry untagged properly.
> > > 
> > > Since the tags in the per-mount tree are not cleared, the inode
> > > shrinker iterates over all AGs that have had reclaimable inodes at one
> > > point in time.
> > > 
> > > The counters on the other hand signal an increasing amount of slab
> > > objects to reclaim.  Since "70e60ce xfs: convert inode shrinker to
> > > per-filesystem context" this is not a real issue anymore because the
> > > shrinker bails out after one iteration.
> > > 
> > > But the problem was observable on a machine running v2.6.34, where the
> > > reclaimable work increased and each process going into direct reclaim
> > > eventually got stuck on the xfs inode shrinking path, trying to scan
> > > several million objects.
> > > 
> > > Fix this by properly unwinding the reclaimable-state tracking of an
> > > inode when it is reclaimed.
> > > 
> > > Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
> > > Cc: stable@kernel.org
> > 
> > Yes, this looks right to me.  The state was correctly
> > adjusted in xfs_iget_cache_hit() when a RECLAIMABLE
> > inode is found in the cache, but it was not done when
> > reclaim completes.
> > 
> > Reviewed-by: Alex Elder <aelder@sgi.com>
> 
> Alex, can you push this to Linus ASAP? This needs to go back to
> stable kernels as well..

Here is my suggestion of a backport to .34.  Dave, Alex, do you
approve?

	Hannes

diff --git a/fs/xfs/xfs_iget.c b/fs/xfs/xfs_iget.c
index 6845db9..3314f2a 100644
--- a/fs/xfs/xfs_iget.c
+++ b/fs/xfs/xfs_iget.c
@@ -499,6 +499,7 @@ xfs_ireclaim(
 	write_lock(&pag->pag_ici_lock);
 	if (!radix_tree_delete(&pag->pag_ici_root, agino))
 		ASSERT(0);
+	pag->pag_ici_reclaimable--;
 	write_unlock(&pag->pag_ici_lock);
 	xfs_perag_put(pag);
 

  reply	other threads:[~2010-10-04 10:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01  7:43 [patch] xfs: properly account for reclaimed inodes Johannes Weiner
2010-10-01 14:02 ` Dave Chinner
2010-10-01 17:17 ` Alex Elder
2010-10-04  7:19   ` Dave Chinner
2010-10-04 10:22     ` Johannes Weiner [this message]
2010-10-05  9:26       ` Hans-Peter Jansen
2010-10-07  3:12         ` Alex Elder
2010-10-06  4:53       ` Dave Chinner
2010-10-06 23:46         ` J.H.

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=20101004102213.GJ2618@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=aelder@sgi.com \
    --cc=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=warthog9@kernel.org \
    --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