2016 49th Annual IEEE/ACM International Symposium on Microarchitecture (MICRO) 2016
DOI: 10.1109/micro.2016.7783764
|View full text |Cite
|
Sign up to set email alerts
|

Continuous runahead: Transparent hardware acceleration for memory intensive workloads

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
90
0

Year Published

2018
2018
2024
2024

Publication Types

Select...
4
3
1

Relationship

1
7

Authors

Journals

citations
Cited by 66 publications
(90 citation statements)
references
References 36 publications
0
90
0
Order By: Relevance
“…In a block group, the metadata block stores the sequence ID (SID), which is the unique number in the memory log area to represent a block group, and the metadata (BLK-1. Note that memory controllers are becoming increasingly more intelligent and complex to deal with various scheduling and performance management issues in multi-core and heterogeneous systems (e.g., [5], [6], [7], [8], [11], [12], [13], [14], [21], [25], [26], [27], [32], [33], [34], [35], [38], [39], [42], [45], [46], [49], [50], [51], [52], [53], [54], [61], [62], [64], [65], [66], [67], [68], [81], [84], [85], [86], [87], [88], [89], [97], [98], [108], [110], [112], [113],…”
Section: Eager Commitmentioning
confidence: 99%
“…In a block group, the metadata block stores the sequence ID (SID), which is the unique number in the memory log area to represent a block group, and the metadata (BLK-1. Note that memory controllers are becoming increasingly more intelligent and complex to deal with various scheduling and performance management issues in multi-core and heterogeneous systems (e.g., [5], [6], [7], [8], [11], [12], [13], [14], [21], [25], [26], [27], [32], [33], [34], [35], [38], [39], [42], [45], [46], [49], [50], [51], [52], [53], [54], [61], [62], [64], [65], [66], [67], [68], [81], [84], [85], [86], [87], [88], [89], [97], [98], [108], [110], [112], [113],…”
Section: Eager Commitmentioning
confidence: 99%
“…This type of code appears in benchmarks such as HashJoin ph2 (hj2). Most hardware prefetchers such as IMP cannot capture these memory accesses, because they require more than one arithmetic/logical operations; expensive hardware prefetchers, e.g., continuous runahead execution [2], can successfully prefetch this type of indirect memory access but only when runahead is sufficiently far and dependence chain can be successfully detected.…”
Section: A[b[i]] and A[b[c[i]]])mentioning
confidence: 99%
“…Each bucket in the hash table consists of a linked list. We used two different variations of this benchmark: (1) Hash Join 2EPB (HJ2) has only one node per bucket and (2). Hash Join 8EPB (HJ8) has three nodes per bucket; as such it performs memory accesses for the additional nodes.…”
Section: Benchmarksmentioning
confidence: 99%
See 1 more Smart Citation
“…Other than explicitly launching a helper thread, many proposals have dealt with reducing the chance a conventional microarchitecture is blocked [2], [13], [14], [19], [30], [38], [39], [41], [51], [55], [69], [73], [100]. Many designs share a theme of checkpointing important state, clean up some structures to allow further (speculative) execution.…”
Section: Background and Related Workmentioning
confidence: 99%