Construct · 1 fields · 1 citations

release consistency: a standalone construct

One name. One construct. A landmark on the map.

● anchor · a standalone construct Nearest construct by meaning·not indexed
releaseconsistency1 CONSTRUCTRelease consistencyGHARACHORLOO · COMPUTER

A single standalone construct; nearby constructs are located against it in the Collider. Tap a field for its definition, unit, and measures.

Computer architecture

a relaxed memory consistency model that guarantees ordering only at acquire and release synchronization operations, allowing more hardware reordering.

In computer architecture, release consistency refers to a relaxed memory consistency model that guarantees ordering only at acquire and release synchronization operations, allowing more hardware reordering. This meaning comes from Gharachorloo (1990) in Proceedings of the 17th annual international symposium on Computer Architecture - ISCA '90.[1]

Unit
Recovery means
Measured by

Next

Run it through the Collider, or take the citations with you.

See how release consistency sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in ColliderExport BibTeXReport this entry

Nearby constructs

architecture3 fields · 4 citationsjingle · one word, three constructsconsistency4 fields · 5 citationsjingle · one word, four constructsmemory consistency model1 fields · 1 citationsanchor · a standalone construct

References

  1. Gharachorloo, K., Lenoski, D., Laudon, J., Gibbons, P., Gupta, A., & Hennessy, J. (1990). Memory consistency and event ordering in scalable shared-memory multiprocessors. Proceedings of the 17th annual international symposium on Computer Architecture - ISCA '90. https://doi.org/10.1145/325164.325102

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct