From: Josh Triplett <josh@joshtriplett.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
niv@us.ibm.com, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
darren@dvhart.com, fweisbec@gmail.com, sbw@mit.edu,
fengguang.wu@intel.com, stephen@networkplumber.org,
davem@davemloft.net, bridge@lists.linux-foundation.org,
netdev@vger.kernel.org, tgraf@suug.ch, gaofeng@cn.fujitsu.com,
linux-decnet-user@lists.sourceforge.net, kuznet@ms2.inr.ac.ru,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net,
linville@tuxdriver.com, johannes@sipsolutions.net
Subject: Re: [PATCH v3 tip/core/rcu 0/14] Sparse-related updates for 3.13
Date: Fri, 11 Oct 2013 23:53:27 -0700 [thread overview]
Message-ID: <20131012065326.GG15339@leaf> (raw)
In-Reply-To: <20131011231659.GA28062@linux.vnet.ibm.com>
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
next prev parent reply other threads:[~2013-10-12 6:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 23:16 [PATCH v3 tip/core/rcu 0/14] Sparse-related updates for 3.13 Paul E. McKenney
[not found] ` <1381533451-29018-1-git-send-email-paulmck@linux.vnet.ibm.com>
2013-10-11 23:17 ` [PATCH v3 tip/core/rcu 03/14] bridge: Apply ACCESS_ONCE() to avoid sparse false positive Paul E. McKenney
2013-10-11 23:17 ` [PATCH v3 tip/core/rcu 04/14] wireless: " Paul E. McKenney
2013-10-11 23:17 ` [PATCH v3 tip/core/rcu 05/14] decnet: " Paul E. McKenney
2013-10-11 23:17 ` [PATCH v3 tip/core/rcu 06/14] ipv4/ip_socketglue: " Paul E. McKenney
2013-10-11 23:17 ` [PATCH v3 tip/core/rcu 07/14] ipv6/ip6_tunnel: " Paul E. McKenney
2013-10-11 23:17 ` [PATCH v3 tip/core/rcu 08/14] ipv6/ip6_gre: " Paul E. McKenney
2013-10-11 23:17 ` [PATCH v3 tip/core/rcu 09/14] ipv6/sit: " Paul E. McKenney
2013-10-11 23:17 ` [PATCH v3 tip/core/rcu 10/14] mac80211: " Paul E. McKenney
2013-10-11 23:17 ` [PATCH v3 tip/core/rcu 11/14] bridge/br_mdb: " Paul E. McKenney
2013-10-11 23:17 ` [PATCH v3 tip/core/rcu 12/14] bonding/bond_main: " Paul E. McKenney
2013-10-11 23:17 ` [PATCH v3 tip/core/rcu 13/14] bonding/bond_alb.c: " Paul E. McKenney
2013-10-12 6:53 ` Josh Triplett [this message]
2013-10-12 17:13 ` [PATCH v3 tip/core/rcu 0/14] Sparse-related updates for 3.13 Paul E. McKenney
2013-10-12 17:39 ` [Bridge] " Hannes Frederic Sowa
2013-10-12 17:43 ` Hannes Frederic Sowa
2013-10-13 11:17 ` Paul E. McKenney
2013-10-13 11:15 ` [Bridge] " 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=20131012065326.GG15339@leaf \
--to=josh@joshtriplett.org \
--cc=akpm@linux-foundation.org \
--cc=bridge@lists.linux-foundation.org \
--cc=darren@dvhart.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fengguang.wu@intel.com \
--cc=fweisbec@gmail.com \
--cc=gaofeng@cn.fujitsu.com \
--cc=jmorris@namei.org \
--cc=johannes@sipsolutions.net \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=laijs@cn.fujitsu.com \
--cc=linux-decnet-user@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niv@us.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sbw@mit.edu \
--cc=stephen@networkplumber.org \
--cc=tglx@linutronix.de \
--cc=tgraf@suug.ch \
--cc=yoshfuji@linux-ipv6.org \
/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).