[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200210120552.1a06a7aa@gandalf.local.home>
Date: Mon, 10 Feb 2020 12:05:52 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
"Joel Fernandes, Google" <joel@...lfernandes.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Gustavo A. R. Silva" <gustavo@...eddedor.com>,
Ingo Molnar <mingo@...hat.com>,
Richard Fontana <rfontana@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
paulmck <paulmck@...nel.org>,
Josh Triplett <josh@...htriplett.org>,
Lai Jiangshan <jiangshanlai@...il.com>,
Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
Subject: Re: [RFC 0/3] Revert SRCU from tracepoint infrastructure
On Mon, 10 Feb 2020 10:46:16 +0100
Peter Zijlstra <peterz@...radead.org> wrote:
> Furthermore, using srcu would be detrimental, because of how it has
> smp_mb() in the read side primitives.
I didn't realize that there was a full memory barrier in the srcu read
side. Seems to me that itself is rational for reverting it. And also a
big NAK for any suggestion to have any of the function tracing to use
it as well (which comes up here and there).
-- Steve
Powered by blists - more mailing lists