Searched refs:barrier (Results 1 – 6 of 6) sorted by relevance
49 void wait() const { barrier.wait(); } in wait()57 mutable Barrier barrier; variable
47 barrier.open(); in handleMessage()
2919 Barrier barrier; member in android::GraphicProducerWrapper2946 barrier.close(); in transact()2951 barrier.wait(); in transact()2966 barrier.open(); in handleMessage()
27 <li style="margin:0"><a href="#membarrier_summry">Memory barrier summary</a></li>33 <li style="margin:0"><a href="#atomic_barrierpairing">Atomic + barrier pairing</a></li>426 and thus have no need for them. (The barrier instructions can be executed but482 <em>store/store barrier</em><br />485 <em>load/load barrier</em><br />490 <p>The store/store barrier guarantees that <strong>all observers</strong> will493 those, so that’s okay. The load/load barrier in thread 2 makes a similar496 <p>Since the store/store barrier guarantees that thread 2 observes the stores in497 program order, why do we need the load/load barrier in thread 2? Because we502 <p>The store/store barrier could work by flushing all[all …]
151 * Compare-and-set operation with a full memory barrier.165 * Compare-and-set operation with a full memory barrier.
194 barrier was restricting how fast SayHi could grow globally. </p>