Proceedings of the 9th Conference on Computing Frontiers 2012
DOI: 10.1145/2212908.2212929
|View full text |Cite
|
Sign up to set email alerts
|

Improving coherence protocol reactiveness by trading bandwidth for latency

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2013
2013
2020
2020

Publication Types

Select...
2
1

Relationship

2
1

Authors

Journals

citations
Cited by 3 publications
(7 citation statements)
references
References 27 publications
0
7
0
Order By: Relevance
“…Nevertheless, multiple timeout dependent core protocol actions (such as persistent request) and semi-centralized arbitration renders this protocol unstable for memory intensive applications. 42 Rainbow is conceived as an extension to Reference 15 which was proposed assuming a single CMP coherence protocol, like many others. 30 A performance comparison with this kind of protocols seems not useful for the discussion (in the context of the class of system considered).…”
Section: Counterpart: Hyper-transport Like Coherence Protocolmentioning
confidence: 99%
“…Nevertheless, multiple timeout dependent core protocol actions (such as persistent request) and semi-centralized arbitration renders this protocol unstable for memory intensive applications. 42 Rainbow is conceived as an extension to Reference 15 which was proposed assuming a single CMP coherence protocol, like many others. 30 A performance comparison with this kind of protocols seems not useful for the discussion (in the context of the class of system considered).…”
Section: Counterpart: Hyper-transport Like Coherence Protocolmentioning
confidence: 99%
“…As a consequence, the chances of evicting an actively shared entry are higher than in numerical applications and consequently so too are the chances of requiring a multicast to reconstruct these entries. Nevertheless, even in the most adverse (and unpractical) directory configurations, this increment is below 20%, which is substantially less than in broadcast coherence protocols [10][14] [25].…”
Section: Sensitivity To Directory Size In a Realistic Private Cachementioning
confidence: 99%
“…Since the directory behaves like a serialization point, concurrent operations initiated by different processors in the same cache block will never end up suffering starvation. In this way, the directory coherence controller will avoid these problems without requiring persistent request [14] or added token tracking facilities [25] [10]. Above all, token counting is useful to filter most of the multicast messages and speed up the directory entry reconstruction.…”
Section: A Conceptual Approachmentioning
confidence: 99%
See 2 more Smart Citations