1990
DOI: 10.1109/32.55094
|View full text |Cite
|
Sign up to set email alerts
|

Memory access dependencies in shared-memory multiprocessors

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
33
0
1

Year Published

1992
1992
2012
2012

Publication Types

Select...
5
3
1

Relationship

1
8

Authors

Journals

citations
Cited by 79 publications
(34 citation statements)
references
References 23 publications
0
33
0
1
Order By: Relevance
“…Some of them [2,29] also relax the store atomicity [5,14] constraint. A write may not be available to all processors at once: it could be at first initiated by a given processor, then committed to a store buffer or a cache, and finally globally performed to memory [22], at which point only it will be available for all processors to see. Hence the value of a given write may be available to certain processors sooner than to others.…”
Section: Weak Memory Modelsmentioning
confidence: 99%
See 1 more Smart Citation
“…Some of them [2,29] also relax the store atomicity [5,14] constraint. A write may not be available to all processors at once: it could be at first initiated by a given processor, then committed to a store buffer or a cache, and finally globally performed to memory [22], at which point only it will be available for all processors to see. Hence the value of a given write may be available to certain processors sooner than to others.…”
Section: Weak Memory Modelsmentioning
confidence: 99%
“…6). This order corresponds roughly to the vendor documentation concept of memory events being globally performed [2,22]: a write in ghb represents the point in global time when this write becomes visible to all processors; whereas a read in ghb represents the point in global time when the read takes place. We will formalise this notion later on, at Sect.…”
Section: Global Happens-beforementioning
confidence: 99%
“…Under a weakly ordered 7 model, invalidations do not cause access penalties as long as the processors await pending invalidations at synchronization points.…”
Section: Release Consistencymentioning
confidence: 99%
“…2.3). This order corresponds roughly to the vendor documentation concept of memory events being globally performed [21,13]: a write in ghb → represents the point in global time when this write becomes visible to all processors; whereas a read in ghb → represents the point in global time when the read takes place. There remain key choices as to which relations we include in ghb → (i.e.…”
Section: Global Happens-beforementioning
confidence: 99%