From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Dmitry Vyukov <dvyukov@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] locking changes for v4.4
Date: Tue, 3 Nov 2015 20:16:44 -0800 [thread overview]
Message-ID: <20151104041644.GO29027@linux.vnet.ibm.com> (raw)
In-Reply-To: <CA+55aFwOgy-_Z64sszX9wUbdj+RBMUNtCu97xOwvHb2w3mnFiA@mail.gmail.com>
On Tue, Nov 03, 2015 at 05:30:29PM -0800, Linus Torvalds wrote:
> On Tue, Nov 3, 2015 at 3:58 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > I think I'll pull this, but then just make a separate commit to remove
> > all the bogus games with "control" dependencies that seem to have no
> > basis is reality.
>
> So the attached is what I committed in my tree. It took much longer to
> try to write the rationale than it took to actually remove the
> atomic_read_ctrl() functions, and even so I'm not sure how good that
> commit message is. But at least it tries to explain what's going on.
>
> Note the final part of the rationale:
>
> I may have to eat my words at some point, but in the absense of clear
> proof that alpha actually needs this, or indeed even an explanation of
> how alpha could _possibly_ need it, I do not believe these functions are
> called for.
>
> And if it turns out that alpha really _does_ need a barrier for this
> case, that barrier still should not be "smp_read_barrier_depends()".
> We'd have to make up some new speciality barrier just for alpha, along
> with the documentation for why it really is necessary.
For whatever it is worth, the patch looks good to me. The reasons I
could imagine why we might want to mark control dependencies are things
like documentation and tooling, but given that we currently only have a
very small number of them, it is hard to argue that this is of immediate
concern, if it is ever of concern.
Thanx, Paul
next prev parent reply other threads:[~2015-11-04 4:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 9:16 [GIT PULL] locking changes for v4.4 Ingo Molnar
2015-11-03 23:54 ` Linus Torvalds
2015-11-03 23:58 ` Linus Torvalds
2015-11-04 1:30 ` Linus Torvalds
2015-11-04 4:16 ` Paul E. McKenney [this message]
2015-11-04 14:51 ` Dmitry Vyukov
2015-11-04 16:01 ` Peter Zijlstra
2015-11-04 16:09 ` Dmitry Vyukov
2015-11-04 11:37 ` Peter Zijlstra
2015-11-04 13:55 ` Paul E. McKenney
2015-11-04 11:48 ` Ingo Molnar
2015-11-04 13:54 ` Paul E. McKenney
2015-11-04 14:56 ` Ingo Molnar
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=20151104041644.GO29027@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--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 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).