Editing Release consistency (section)

=== Example ===
Consider the scenarios described in the image to the right. This case shows when write propagation is performed on a cache-coherent system based on the release consistency model. The variable ''datum'' is completely propagated before the propagation of ''datumIsReady.'' But the value of ''datum'' is not needed until after the acquire synchronization access in P1 and it can be propagated along with ''datumIsReady'' without harming the result of the program.

[[File:Lazy RC.png|thumb|400x400px|Write propagation in lazy release consistency model]]
The second image displays what is the case when lazy release consistency is applied. Considering this scenario, all values written ahead of the release synchronization are delayed and propagated together with the propagation of the release access itself. Hence, ''datum'' and ''datumIsReady'' are propagated together at the release point.

"TreadMarks"<ref>[http://dl.acm.org/citation.cfm?id=1267084 ''TreadMarks: distributed shared memory on standard workstations and operating systems''] by Pete Keleher, Alan L. Cox, [[Sandhya Dwarkadas]] and Willy Zwaenepoel published in WTEC'94 Proceedings of the USENIX Winter 1994 Technical Conference on USENIX Winter 1994 Technical Conference</ref> is an actual application of lazy release consistency.