From: Peter Zijlstra <peterz@infradead.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
dipankar <dipankar@in.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Josh Triplett <josh@joshtriplett.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt <rostedt@goodmis.org>,
David Howells <dhowells@redhat.com>,
Eric Dumazet <edumazet@google.com>,
dvhart <dvhart@linux.intel.com>, fweisbec <fweisbec@gmail.com>,
Oleg Nesterov <oleg@redhat.com>,
bobby prani <bobby.prani@gmail.com>, ldr709 <ldr709@gmail.com>
Subject: Re: [PATCH RFC tip/core/rcu] SRCU rewrite
Date: Tue, 15 Nov 2016 15:55:36 +0100 [thread overview]
Message-ID: <20161115145536.GE11311@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20161115142627.GX4127@linux.vnet.ibm.com>
On Tue, Nov 15, 2016 at 06:26:27AM -0800, Paul E. McKenney wrote:
> On Tue, Nov 15, 2016 at 02:59:12PM +0100, Peter Zijlstra wrote:
> > The smp_mb()s in read_{un,}lock() and the lock in call_srcu() come to
> > mind.
>
> There is some possibility of weakening the srcu_read_unlock() ordering,
> but one step at a time.
>
> Has the lock in call_srcu() been causing trouble? Easy to fix if so,
> but as you noted in another email today, we don't need complexity for
> complexity's sake. And no reports of problems with this have reached
> me thus far.
It was a cause for concern in the optimistic fault series, but since
that never got sorted, it hasn't shown up in practise afaik.
next prev parent reply other threads:[~2016-11-15 14:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 18:36 [PATCH RFC tip/core/rcu] SRCU rewrite Paul E. McKenney
2016-11-14 19:00 ` Mathieu Desnoyers
2016-11-15 1:44 ` Boqun Feng
2016-11-15 14:37 ` Paul E. McKenney
2016-11-17 12:18 ` Lai Jiangshan
2016-11-17 13:49 ` Paul E. McKenney
2016-11-17 14:38 ` Paul E. McKenney
2016-11-17 14:45 ` Boqun Feng
2016-11-17 15:54 ` Paul E. McKenney
2016-11-17 15:55 ` Lai Jiangshan
2016-11-17 17:42 ` Paul E. McKenney
2016-11-17 14:31 ` Boqun Feng
2016-11-17 15:03 ` Paul E. McKenney
2016-11-17 15:07 ` Lai Jiangshan
2016-11-17 15:31 ` Mathieu Desnoyers
2016-11-17 15:38 ` Mathieu Desnoyers
2016-11-17 15:53 ` Paul E. McKenney
2016-11-17 16:33 ` Mathieu Desnoyers
2016-11-17 20:31 ` Lance Roy
2016-11-15 7:51 ` Peter Zijlstra
2016-11-15 13:54 ` Mathieu Desnoyers
2016-11-15 13:59 ` Peter Zijlstra
2016-11-15 14:26 ` Paul E. McKenney
2016-11-15 14:55 ` Peter Zijlstra [this message]
2016-11-15 15:43 ` Paul E. McKenney
2016-11-17 13:58 ` Lai Jiangshan
2016-11-17 19:53 ` Lance Roy
2016-11-18 13:27 ` Paul E. McKenney
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=20161115145536.GE11311@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=ldr709@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--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 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.