2013
DOI: 10.1145/2541228.2541235
|View full text |Cite
|
Sign up to set email alerts
|

Using in-flight chains to build a scalable cache coherence protocol

Abstract: As microprocessor designs integrate more cores, scalability of cache coherence protocols becomes a challenging problem. Most directory-based protocols avoid races by using blocking tag directories that can impact the performance of parallel applications. In this article, we first quantitatively demonstrate that state-of-the-art blocking protocols significantly constrain throughput at large core counts for several parallel applications. Nonblocking protocols address this throughput concern at the expense of sca… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2015
2015
2015
2015

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(1 citation statement)
references
References 47 publications
0
1
0
Order By: Relevance
“…When the pending registration's ack arrives, the cache services the stored request in its MSHR, forwarding the registration ack (or data for a read) to the requesting core (keeping itself invalid). Thus, instead of serializing registrations at the LLC, we build a queue distributed among the L1 caches with pending registrations (similar to [12,13,34]). 2 Summary and Example: In summary, the DeNovoSync0 protocol effectively treats a synchronization read like a readmodify-write (RMW), requiring registration.…”
Section: The Denovosync0 Protocolmentioning
confidence: 99%
“…When the pending registration's ack arrives, the cache services the stored request in its MSHR, forwarding the registration ack (or data for a read) to the requesting core (keeping itself invalid). Thus, instead of serializing registrations at the LLC, we build a queue distributed among the L1 caches with pending registrations (similar to [12,13,34]). 2 Summary and Example: In summary, the DeNovoSync0 protocol effectively treats a synchronization read like a readmodify-write (RMW), requiring registration.…”
Section: The Denovosync0 Protocolmentioning
confidence: 99%