From: Tim Chen <tim.c.chen@linux.intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
Dave Chinner <dchinner@redhat.com>,
Dave Hansen <dave.hansen@intel.com>,
Andi Kleen <ak@linux.intel.com>,
Matthew Wilcox <willy@linux.intel.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH] Avoid useless inodes and dentries reclamation
Date: Fri, 06 Sep 2013 11:26:45 -0700 [thread overview]
Message-ID: <1378492005.3467.9.camel@schen9-DESK> (raw)
In-Reply-To: <20130906005524.GA23571@dastard>
On Fri, 2013-09-06 at 10:55 +1000, Dave Chinner wrote:
> On Tue, Sep 03, 2013 at 11:38:27AM -0700, Tim Chen wrote:
> > On Sat, 2013-08-31 at 19:00 +1000, Dave Chinner wrote:
> > > On Fri, Aug 30, 2013 at 09:21:34AM -0700, Tim Chen wrote:
> > > >
> > > >
> > > > Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
> > > > ---
> > > > diff --git a/fs/super.c b/fs/super.c
> > > > index 73d0952..4df1fab 100644
> > > > --- a/fs/super.c
> > > > +++ b/fs/super.c
> > > > @@ -112,9 +112,6 @@ static unsigned long super_cache_count(struct shrinker *shrink,
> > > >
> > > > sb = container_of(shrink, struct super_block, s_shrink);
> > > >
> > > > - if (!grab_super_passive(sb))
> > > > - return 0;
> > > > -
> > >
> > > I think the function needs a comment explaining why we aren't
> > > grabbing the sb here, otherwise people are going to read the code
> > > and ask why it's different to the scanning callout.
> > >
> > > > if (sb->s_op && sb->s_op->nr_cached_objects)
> > > > total_objects = sb->s_op->nr_cached_objects(sb,
> > > > sc->nid);
> > >
> >
> > Yes, those comments are needed.
> > I also need to remove the corresponding
> > drop_super(sb);
> >
> > So probably something like:
> >
> > ---
> > diff --git a/fs/super.c b/fs/super.c
> > index 73d0952..7b5a6e5 100644
> > --- a/fs/super.c
> > +++ b/fs/super.c
> > @@ -112,9 +112,14 @@ static unsigned long super_cache_count(struct shrinker *shrink,
> >
> > sb = container_of(shrink, struct super_block, s_shrink);
> >
> > - if (!grab_super_passive(sb))
> > - return 0;
> > -
> > + /*
> > + * Don't call grab_super_passive as it is a potential
> > + * scalability bottleneck. The counts could get updated
> > + * between super_cache_count and super_cache_scan anyway.
> > + * Call to super_cache_count with shrinker_rwsem held
> > + * ensures the safety of call to list_lru_count_node() and
> > + * s_op->nr_cached_objects().
> > + */
>
> Well, that's not true of s_op->nr_cached_objects() right now. It's
> only going to be true if the shrinker deregistration is moved before
> ->kill_sb()....
>
> > > Let me have a bit more of a think about this - the solution may
> > > simply be unregistering the shrinker before we call ->kill_sb() so
> > > the shrinker can't get called while we are tearing down the fs.
> > > First, though, I need to go back and remind myself of why I put that
> > > after ->kill_sb() in the first place.
> >
> > Seems very reasonable as I haven't found a case where the shrinker
> > is touched in ->kill_sb() yet. It looks like unregistering the
> > shrinker before ->kill_sb() should be okay.
>
> Having looked at it some more, I have to agree. I think the original
> reason for unregistering the shrinker there was to avoid problems
> with locking - the shrinker callouts are run holding the
> shrinker_rwsem in read mode, and then we lock the sb->s_umount in
> read mount. In the unmount case, we currently take the sb->s_umount
> lock in write mode (thereby locking out the shrinker) but we drop it
> before deregistering the shrinker and so there is no inverted
> locking order.
>
> The thing is, grab_super_passive does a try-lock on the sb->s_umount
> now, and so if we are in the unmount process, it won't ever block.
> That means what used to be a deadlock and races we were avoiding
> by using grab_super_passive() is now:
>
> shrinker umount
>
> down_read(shrinker_rwsem)
> down_write(sb->s_umount)
> shrinker_unregister
> down_write(shrinker_rwsem)
> <blocks>
> grab_super_passive(sb)
> down_read_trylock(sb->s_umount)
> <fails>
> <shrinker aborts>
> ....
> <shrinkers finish running>
> up_read(shrinker_rwsem)
> <unblocks>
> <removes shrinker>
> up_write(shrinker_rwsem)
> ->kill_sb()
> ....
>
> And so it appears to be safe to deregister the shrinker before
> ->kill_sb().
>
> Can you do this as two patches? The first moves the shrinker
> deregistration to before ->kill_sb(), then second is the above patch
> that drops the grab-super_passive() calls from the ->count_objects
> function?
I've sent the patches on a separate mail thread. Please add
your sign-off if the patches look okay.
Thanks.
Tim
prev parent reply other threads:[~2013-09-06 18:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 21:52 [PATCH] Avoid useless inodes and dentries reclamation Tim Chen
2013-08-28 21:19 ` Kirill A. Shutemov
2013-08-28 22:54 ` Tim Chen
2013-08-29 11:07 ` Dave Chinner
2013-08-29 18:07 ` Tim Chen
2013-08-29 18:36 ` Dave Hansen
2013-08-30 1:56 ` Dave Chinner
2013-08-30 1:40 ` Dave Chinner
2013-08-30 16:21 ` Tim Chen
2013-08-31 9:00 ` Dave Chinner
2013-09-03 18:38 ` Tim Chen
2013-09-06 0:55 ` Dave Chinner
2013-09-06 18:26 ` Tim Chen [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=1378492005.3467.9.camel@schen9-DESK \
--to=tim.c.chen@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.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).