linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
	linux-xfs@vger.kernel.org, Nikolay Borisov <nborisov@suse.com>,
	Jan Kara <jack@suse.cz>, Michal Hocko <mhocko@suse.com>
Subject: Re: Reviewing determinism of xfs_reclaim_inodes_ag()
Date: Wed, 26 Apr 2017 11:12:06 +0200	[thread overview]
Message-ID: <20170426091206.GA28800@wotan.suse.de> (raw)
In-Reply-To: <20170426000426.GK12369@dastard>

On Wed, Apr 26, 2017 at 10:04:26AM +1000, Dave Chinner wrote:
> On Tue, Apr 25, 2017 at 10:25:03AM +0200, Luis R. Rodriguez wrote:
> > I checked with Jan Kara and he believes the current code is correct but that
> > its the comment that that may be misleading. As per Jan the race is between
> > getting an inode reclaimed and grabbing it. Ie, XFS frees the inodes by RCU.
> > However it doesn't actually *reuse* the inode until RCU period passes
> > (unlike inodes allocated from slab with SLAB_RCU can be). So it can happen
> 
> ..... I initially tried using SLAB_DESTROY_BY_RCU which meant the
> RCU grace period did not prevent reallocation of inodes that had
> been freed. Hence this check was (once) necessary to prevent the
> reclaim index going whacky on a reallocated inode.

Alright this helps, but why does *having* the RCU grace period prevent
such type of race ? I can see it helping but removing completely such
a race as a possibility ? Also, just so I understand I am following, this
then implicates our reclaim rate is directly linked to the RCU grace
period ?

  Luis

  parent reply	other threads:[~2017-04-26  9:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25  8:25 Reviewing determinism of xfs_reclaim_inodes_ag() Luis R. Rodriguez
2017-04-26  0:04 ` Dave Chinner
2017-04-26  7:34   ` Jan Kara
2017-04-26  9:12   ` Luis R. Rodriguez [this message]
2017-04-26 10:55     ` Jan Kara
2017-05-06 17:41       ` Luis R. Rodriguez
2017-05-06 17:52         ` Luis R. Rodriguez
2017-05-09 10:41           ` Jan Kara

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=20170426091206.GA28800@wotan.suse.de \
    --to=mcgrof@kernel.org \
    --cc=david@fromorbit.com \
    --cc=jack@suse.cz \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mhocko@suse.com \
    --cc=nborisov@suse.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;
as well as URLs for NNTP newsgroup(s).