1991
DOI: 10.21236/ada237629
|View full text |Cite
|
Sign up to set email alerts
|

LimitLESS Directories: A Scalable Cache Coherence Scheme

Abstract: Caches enhance the performance of multiprocessors by reducing network tra c and average memory access latency. However, cache-based systems must address the problem of cache coherence. We propose the LimitLESS directory protocol to solve this problem. The LimitLESS scheme uses a combination of hardware and software techniques to realize the performance of a full-map directory with the memory overhead of a limited directory. This protocol is supported by Alewife, a large-scale multiprocessor. We describe the ar… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
87
0
3

Year Published

1996
1996
2015
2015

Publication Types

Select...
6
2

Relationship

1
7

Authors

Journals

citations
Cited by 64 publications
(91 citation statements)
references
References 3 publications
1
87
0
3
Order By: Relevance
“…DSMs typically employ cache-coherence protocols that are directory based 15,32,3,14,63 . Directorybased cache-coherence protocols maintain a directory entry for each cache block of data 26 CHAPTER 2.…”
Section: Cache Coherencementioning
confidence: 99%
See 2 more Smart Citations
“…DSMs typically employ cache-coherence protocols that are directory based 15,32,3,14,63 . Directorybased cache-coherence protocols maintain a directory entry for each cache block of data 26 CHAPTER 2.…”
Section: Cache Coherencementioning
confidence: 99%
“…Initially, before time t0, the processor is executing non-MGS code, indicated by a bar lled with a hash pattern. This code executes in context C0 Once running, the rst thing the handler does is turn on interrupts 15 . Then, it performs some work which is timed by some statistics instrumentation code.…”
Section: Statisticsmentioning
confidence: 99%
See 1 more Smart Citation
“…3.4 to simplify our implementation. Directory state: Conventional directories must track both the sharers of each line (using a bit-vector or other techniques [13,53,66]), and, if there is a single sharer, whether it has exclusive or read-only permission. In Coup, the directory must track whether sharers have exclusive, read-only, or update-only permission.…”
Section: Structural Changesmentioning
confidence: 99%
“…We will refer to these proposals as compressed sharing codes (also known as multicast protocols [16] and limited broadcast protocols [1]), as opposed to exact ones (as limited pointers [4] or…”
Section: ¢ ¡ ¤ £ ¥mentioning
confidence: 99%