Editing Release consistency (section)

=== Conditions for sequential consistent result ===
In general, a distributed shared memory is release consistent if it obeys the following rules:<ref>{{Cite book|title=Distributed Operating Systems|last=Tanenbaum|first=Andrew|publisher=Pearson Education|year=1995|isbn=9788177581799|pages=327–330}}</ref>

1. Before an access to a shared variable is performed, all previous acquires by this processor must have completed.

2. Before a release is performed, all previous reads and writes by this process must have completed.

3. The acquire and release accesses must be [[Processor consistency|processor consistent]].

If the conditions above are met and the program is properly synchronized (i.e., processors implement acquire and release properly), the results of any execution will be exactly the same as they would have been executed following sequential consistency. In effect, accesses to shared variables are separated into atomic operation blocks by the ''acquire'' and ''release'' primitives so that races and interleaving between blocks will be prevented.