[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131012065326.GG15339@leaf>
Date: Fri, 11 Oct 2013 23:53:27 -0700
From: Josh Triplett <josh@...htriplett.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, mingo@...nel.org,
laijs@...fujitsu.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
niv@...ibm.com, tglx@...utronix.de, peterz@...radead.org,
rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com,
darren@...art.com, fweisbec@...il.com, sbw@....edu,
fengguang.wu@...el.com, stephen@...workplumber.org,
davem@...emloft.net, bridge@...ts.linux-foundation.org,
netdev@...r.kernel.org, tgraf@...g.ch, gaofeng@...fujitsu.com,
linux-decnet-user@...ts.sourceforge.net, kuznet@....inr.ac.ru,
jmorris@...ei.org, yoshfuji@...ux-ipv6.org, kaber@...sh.net,
linville@...driver.com, johannes@...solutions.net
Subject: Re: [PATCH v3 tip/core/rcu 0/14] Sparse-related updates for 3.13
On Fri, Oct 11, 2013 at 04:16:59PM -0700, Paul E. McKenney wrote:
> Changes from v2:
>
> o Switch from rcu_assign_pointer() to ACCESS_ONCE() given that
> the pointers are all --rcu and already visible to readers,
> as suggested by Eric Dumazet and Josh Triplett.
Hang on a moment. Do *none* of these cases need write memory barriers?
- Josh Triplet
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists