From: Peter Zijlstra <peterz@infradead.org>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Jason Low <jason.low2@hpe.com>, Waiman Long <waiman.long@hpe.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, Dave Chinner <david@fromorbit.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Scott J Norton <scott.norton@hpe.com>,
Douglas Hatch <doug.hatch@hpe.com>,
jason.low2@hp.com
Subject: Re: [PATCH v4 2/5] locking/rwsem: Protect all writes to owner by WRITE_ONCE
Date: Sun, 22 May 2016 12:42:23 +0200 [thread overview]
Message-ID: <20160522104223.GO3193@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <574086FE.6080807@hurleysoftware.com>
On Sat, May 21, 2016 at 09:04:14AM -0700, Peter Hurley wrote:
> And by the way, it's not just "here" but _everywhere_.
> What about reading ->on_cpu locklessly?
In the smp_cond_acquire() rework that I have pending that one is
actually 'fixed'.
But yeah, the whole load/store tearing thing is giant pain inflicted
upon us by C language and GCC people :/
And the problem is that the 'regression' is now so old it doesn't matter
they fix it or not, we have to support compilers that think its fine to
generates tears :-(
next prev parent reply other threads:[~2016-05-22 10:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 1:26 [PATCH v4 0/5] [PATCH v3 0/4] locking/rwsem: Add reader-owned state to the owner field Waiman Long
2016-05-18 1:26 ` [PATCH v4 1/5] " Waiman Long
2016-06-06 17:18 ` Davidlohr Bueso
2016-06-06 20:03 ` Waiman Long
2016-06-06 21:02 ` Peter Zijlstra
2016-06-06 21:49 ` Waiman Long
2016-06-08 14:25 ` [tip:locking/core] " tip-bot for Waiman Long
2016-05-18 1:26 ` [PATCH v4 2/5] locking/rwsem: Protect all writes to owner by WRITE_ONCE() Waiman Long
2016-05-18 14:04 ` Davidlohr Bueso
2016-05-18 17:21 ` [PATCH v4 2/5] locking/rwsem: Protect all writes to owner by WRITE_ONCE Jason Low
2016-05-18 18:29 ` Waiman Long
2016-05-18 19:58 ` Jason Low
2016-05-19 22:21 ` Jason Low
2016-05-20 20:26 ` Waiman Long
2016-05-21 16:04 ` Peter Hurley
2016-05-22 10:42 ` Peter Zijlstra [this message]
2016-05-23 18:46 ` Jason Low
2016-05-23 19:44 ` Davidlohr Bueso
2016-05-23 20:15 ` Paul E. McKenney
2016-05-23 21:04 ` Davidlohr Bueso
2016-05-25 1:25 ` Waiman Long
2016-05-18 17:23 ` [PATCH v4 2/5] locking/rwsem: Protect all writes to owner by WRITE_ONCE() Jason Low
2016-06-08 14:25 ` [tip:locking/core] " tip-bot for Waiman Long
2016-05-18 1:26 ` [PATCH v4 3/5] locking/rwsem: Don't wake up one's own task Waiman Long
2016-05-18 10:30 ` Peter Zijlstra
2016-05-18 16:04 ` Waiman Long
2016-05-18 1:26 ` [PATCH v4 4/5] locking/rwsem: Improve reader wakeup code Waiman Long
2016-06-08 14:25 ` [tip:locking/core] " tip-bot for Waiman Long
2016-05-18 1:26 ` [PATCH v4 5/5] locking/rwsem: Streamline the rwsem_optimistic_spin() code Waiman Long
2016-06-08 14:26 ` [tip:locking/core] " tip-bot for Waiman Long
2016-05-18 10:52 ` [PATCH v4 0/5] [PATCH v3 0/4] locking/rwsem: Add reader-owned state to the owner field Peter Zijlstra
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=20160522104223.GO3193@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dave@stgolabs.net \
--cc=david@fromorbit.com \
--cc=doug.hatch@hpe.com \
--cc=jason.low2@hp.com \
--cc=jason.low2@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peter@hurleysoftware.com \
--cc=scott.norton@hpe.com \
--cc=waiman.long@hpe.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