[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170811090601.2owslxi4lgv3kond@hirez.programming.kicks-ass.net>
Date: Fri, 11 Aug 2017 11:06:01 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Waiman Long <longman@...hat.com>
Cc: Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
Pan Xinhui <xinhui@...ux.vnet.ibm.com>,
Boqun Feng <boqun.feng@...il.com>,
Andrea Parri <parri.andrea@...il.com>,
Will Deacon <will.deacon@....com>
Subject: Re: [RESEND PATCH v5] locking/pvqspinlock: Relax cmpxchg's to
improve performance on some archs
On Thu, Aug 10, 2017 at 02:18:30PM -0400, Waiman Long wrote:
> On 08/10/2017 12:22 PM, Waiman Long wrote:
> > On 08/10/2017 12:15 PM, Peter Zijlstra wrote:
> >> Might as well do an explicit:
> >>
> >> smp_mb__before_atomic()
> >> cmpxchg_relaxed()
> >> smp_mb__after_atomic()
> >>
> >> I suppose and not introduce new primitives.
>
> I think we don't need smp_mb__after_atomic(). The read has to be fully
> ordered, but the write part may not need it as the control dependency of
> the old value should guard against incorrect action. Right?
You'd think that, but IIRC there was something funny about using the SC
return flag for control dependencies. Will?
Powered by blists - more mailing lists