lkml.org 
[lkml]   [2015]   [Oct]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2] barriers: introduce smp_mb__release_acquire and update documentation
On Fri, Oct 09, 2015 at 01:02:46PM +0200, Peter Zijlstra wrote:
> On Fri, Oct 09, 2015 at 10:40:39AM +0100, Will Deacon wrote:
> > Stepping back a second, I believe that there are three cases:
> >
> >
> > RELEASE X -> ACQUIRE Y (same CPU)
> > * Needs a barrier on TSO architectures for full ordering
> +PPC
>
> > UNLOCK X -> LOCK Y (same CPU)
> > * Needs a barrier on PPC for full ordering
>
>
> > RELEASE X -> ACQUIRE X (different CPUs)
> * Fully ordered everywhere...
> * ... but needs a barrier on TSO + PPC to become a full barrier
>
> > UNLOCK X -> ACQUIRE X (different CPUs)
>
> s/ACQUIRE/LOCK/ ?

Yes, sorry.

Will


\
 
 \ /
  Last update: 2015-10-09 15:01    [W:1.010 / U:0.800 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site