Lines Matching full:consistency
13 <li style="margin: 3px 0 0"><a href="#mem_consistency">Memory consistency models</a>
15 <li style="margin:0"><a href="#proc_consistency">Processor consistency</a></li>
26 <li style="margin:0"><a href="#addr_dep">Address dependencies and causal consistency</a></li>
117 <h3 id="mem_consistency">Memory consistency models</h3>
119 <p>Memory consistency models, or often just ?memory models?, describe the
126 consistency</em>, which is described like this <span
177 <p>Sequential consistency guarantees that, after both threads have finished
211 <h4 id="proc_consistency">Processor consistency</h4>
213 <p>x86 SMP provides <em>processor consistency</em>, which is slightly weaker than
308 by the CPU architecture?s <em>cache consistency model</em>.</p>
316 <p>For the memory consistency model to be sequentially consistent, core 1 would
324 <p>The other guarantees made by the processor consistency model are less
352 consistency model doesn?t dictate when something completes, just when it can be
388 <p>ARM SMP provides weak memory consistency guarantees. It does not guarantee that
425 access ordering matters. ARM/x86 uniprocessors offer sequential consistency,
602 <h4 id="addr_dep">Address dependencies and causal consistency</h4>
682 you can?t think about consistency issues in terms of instruction execution.
686 consistency</em>:</p>
1047 <p>Debugging memory consistency problems can be very difficult. If a missing
1064 locations. Combine that with the sequential consistency provided by the
1815 <dt>Shared Memory Consistency Models: A Tutorial</dt>
1816 <dd>Written in 1995 by Adve & Gharachorloo, this is a good place to start if you want to dive more deeply into memory consistency models.
1836 <dd>The documentation for the <code>java.util.concurrent</code> package. Near the bottom of the page is a section entitled ?Memory Consistency Properties? that explains the guarantees made by the various classes.
