1982
DOI: 10.1145/1067649.801739
|View full text |Cite
|
Sign up to set email alerts
|

Effects of cache coherency in multiprocessors

Abstract: In many commercial multiprocessor systems, each processor accesses the memory through a private cache. One problem that could limit the extensibility of the system and its performance is the enforcement of cache coherence. A mechanism must exist which prevents the existence of several different copies of the same data block in different private caches. In this paper, we present an indepth analysis of the effect of cache coherency in multiprocessors. A novel analytical model for the program behavior of a multit… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
12
0
1

Year Published

1989
1989
2018
2018

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 12 publications
(13 citation statements)
references
References 8 publications
0
12
0
1
Order By: Relevance
“…Un répertoire centralisé consiste à maintenir dans un tableau partagé l'état courant des blocs mémoires répartis entre tous les processeurs (Censier et al, 1978;Dubois et al, 1982). Cette solution, largement utilisée dans les architectures à haute performance, engendre cependant un surcoût temporel important, pénalisant fortement les performances de l'architecture.…”
Section: Gestion De La Cohérenceunclassified
“…Un répertoire centralisé consiste à maintenir dans un tableau partagé l'état courant des blocs mémoires répartis entre tous les processeurs (Censier et al, 1978;Dubois et al, 1982). Cette solution, largement utilisée dans les architectures à haute performance, engendre cependant un surcoût temporel important, pénalisant fortement les performances de l'architecture.…”
Section: Gestion De La Cohérenceunclassified
“…The system workload model consists of two memory reference streams, one to private blocks and another to shared blocks. Dubois and Briggs [ 1982] used an independent reference model (IRM) for shared-block accesses and a least recently used stack model (LRUSM) for private block accesses. An IRM for shared-block accesses is not adopted here since it does not capture any locality.…”
Section: Workload Modelmentioning
confidence: 99%
“…One approach is a "static coherence check," which avoids multiple copies of shared variables and allows only one copy of global variables. A second approach is "dynamic coherence check," in which multiplecopiesof global variables are allowed, but they are discarded when the global variables are modified [54]. A more systematic approach is proposed in [55], in which the compiler detects the variables that can cause a coherence problem and carefully allows multiple copies of them.…”
Section: ) Memory Allocationmentioning
confidence: 99%