From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "J. R. Okajima" <hooanon05g@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
George Spelvin <linux@sciencehorizons.net>
Subject: Re: Q. hlist_bl_add_head_rcu() in d_alloc_parallel()
Date: Sat, 25 Jun 2016 23:54:24 +0100 [thread overview]
Message-ID: <20160625225423.GV14480@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFzwaiLbT8LrQTnktGdoizc9uuRbfe4cvdykXO_K8Kj2aQ@mail.gmail.com>
On Thu, Jun 23, 2016 at 10:57:09PM -0700, Linus Torvalds wrote:
> The non-RCU case basically never shows up in profiles (it used to,
> with symlinks, but you fixed that case), and if it ever does I suspect
> that the fix will be to make sure we don't fall out of rcu.
>
> So don't worry too much about __d_lookup() being a hot case, I don't
> think it is.
>
> (Of course, if you have a load that shows me wrong, let's look at it
> by all means. Maybe the loads I have used have been bad)
BTW, speaking of that area - is there any reason why dentry_cmp()
isn't simply
return dentry_string_cmp(lockless_dereference(dentry->d_name.name),
ct, tcount);
other than "it predates lockless_dereference()"?
The only difference is s/ACCESS_ONCE/READ_ONCE/, AFAICS -
lockless_dereference() uses the latter these days. And that shouldn't
be a problem; as the matter of fact, *all* remaining ACCESS_ONCE in
fs/dcache.c look like they should become READ_ONCE. Objections?
Al, digging through the barrier-related issues with dentries and peeling the
paint off the walls in process...
next prev parent reply other threads:[~2016-06-25 22:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 20:50 Q. hlist_bl_add_head_rcu() in d_alloc_parallel() J. R. Okajima
2016-06-17 22:16 ` Al Viro
2016-06-17 22:56 ` Al Viro
2016-06-19 5:24 ` J. R. Okajima
2016-06-19 16:55 ` Al Viro
2016-06-20 4:34 ` J. R. Okajima
2016-06-20 5:35 ` Al Viro
2016-06-20 14:51 ` Al Viro
2016-06-20 17:14 ` [git pull] vfs fixes Al Viro
2016-06-23 1:19 ` Q. hlist_bl_add_head_rcu() in d_alloc_parallel() J. R. Okajima
2016-06-23 2:58 ` Al Viro
2016-06-24 5:57 ` Linus Torvalds
2016-06-25 22:54 ` Al Viro [this message]
2016-06-26 1:25 ` Linus Torvalds
2016-06-29 8:17 ` Al Viro
2016-06-29 9:22 ` Hekuang
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=20160625225423.GV14480@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hooanon05g@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux@sciencehorizons.net \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.