Re: [PATCH tip/core/rcu 12/15] rcu: Remove redundant memory barrier from __call_rcu()

2012-08-31 Thread Josh Triplett
On Fri, Aug 31, 2012 at 11:30:35AM -0700, Josh Triplett wrote: > On Thu, Aug 30, 2012 at 11:56:25AM -0700, Paul E. McKenney wrote: > > From: "Paul E. McKenney" > > > > The first memory barrier in __call_rcu() is supposed to order any > > updates done beforehand by the caller against the actual qu

Re: [PATCH tip/core/rcu 12/15] rcu: Remove redundant memory barrier from __call_rcu()

2012-08-31 Thread Josh Triplett
On Thu, Aug 30, 2012 at 11:56:25AM -0700, Paul E. McKenney wrote: > From: "Paul E. McKenney" > > The first memory barrier in __call_rcu() is supposed to order any > updates done beforehand by the caller against the actual queuing > of the callback. However, the second memory barrier (which is in

[PATCH tip/core/rcu 12/15] rcu: Remove redundant memory barrier from __call_rcu()

2012-08-30 Thread Paul E. McKenney
From: "Paul E. McKenney" The first memory barrier in __call_rcu() is supposed to order any updates done beforehand by the caller against the actual queuing of the callback. However, the second memory barrier (which is intended to order incrementing the queue lengths before queuing the callback)