From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] locking changes for v4.4
Date: Tue, 3 Nov 2015 15:58:54 -0800 [thread overview]
Message-ID: <CA+55aFzkn4-s5r2Wpkm_rKz5cAZXWjRoK_+EL9hC32ZTourmtw@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFzVU_T1LRF_udR_h1eKOkXuZ9h=D5w7iKcXH5TmwqG_hQ@mail.gmail.com>
On Tue, Nov 3, 2015 at 3:54 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Tue, Nov 3, 2015 at 1:16 AM, Ingo Molnar <mingo@kernel.org> wrote:
>>
>> - More gradual enhancements to atomic ops: new atomic*_read_ctrl() ops,
>> synchronize atomic_{read,set}() ordering requirements between architectures,
>> add atomic_long_t bitops. (Peter Zijlstra)
>
> From another thread: those new "atomic*_read_ctrl()" operations are
> complete voodoo programming, and should never ever be used.
Sadly, that commit seems to be in the middle of the series.
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.
Linus
next prev parent reply other threads:[~2015-11-03 23:58 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 [this message]
2015-11-04 1:30 ` Linus Torvalds
2015-11-04 4:16 ` Paul E. McKenney
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=CA+55aFzkn4-s5r2Wpkm_rKz5cAZXWjRoK_+EL9hC32ZTourmtw@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@us.ibm.com \
--cc=tglx@linutronix.de \
/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).