From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: NeilBrown <neilb@suse.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <Anna.Schumaker@netapp.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH/RFC] VFS: don't keep disconnected dentries on d_anon
Date: Thu, 21 Dec 2017 05:40:00 +0000 [thread overview]
Message-ID: <20171221054000.GX21978@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFw98_-SRszjy4dh97VhnZeOMpcVVzS8Mvew2b9juYDTmg@mail.gmail.com>
On Wed, Dec 20, 2017 at 04:57:28PM -0800, Linus Torvalds wrote:
> On Wed, Dec 20, 2017 at 2:45 PM, NeilBrown <neilb@suse.com> wrote:
> >
> > We could just leave the code unchanged, but apart from that being
> > potentially confusing, the (unfair) bit-spin-lock which protects
> > s_anon can become a bottle neck when lots of disconnected dentries are
> > being created.
> >
> > So this patch renames s_anon to s_roots, and stops storing
> > disconnected dentries on the list. Only dentries obtained with
> > d_obtain_root() are now stored on this list. There are many fewer of
> > these (only NFS and NILFS2 use the call, and only during filesystem
> > mount) so contention on the bit-lock will not be a problem.
>
> Thanks, Neil. This is much nicer than the magical special case patch
> for s_anon bitlock.
>
> Al, I'm going to assume I'll get this through your vfs tree (with
> whatever edits from the comments people made).
*nod*
I've got sidetracked digging through the Lustre mess with dcache (revalidation
stuff, again), will finish once I get some sleep. In any case, I like that
variant; it's definitely going to be applied.
next prev parent reply other threads:[~2017-12-21 5:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 22:45 [PATCH/RFC] VFS: don't keep disconnected dentries on d_anon NeilBrown
2017-12-20 22:56 ` Matthew Wilcox
2017-12-20 23:13 ` NeilBrown
2017-12-20 23:16 ` Al Viro
2017-12-21 0:57 ` Linus Torvalds
2017-12-21 5:40 ` Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-20 22:45 NeilBrown
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=20171221054000.GX21978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Anna.Schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.com \
--cc=torvalds@linux-foundation.org \
--cc=trond.myklebust@primarydata.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).