2022 IEEE International Symposium on High-Performance Computer Architecture (HPCA) 2022
DOI: 10.1109/hpca53966.2022.00070
|View full text |Cite
|
Sign up to set email alerts
|

ASAP: A Speculative Approach to Persistence

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
2
0

Year Published

2022
2022
2024
2024

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 12 publications
(2 citation statements)
references
References 36 publications
0
2
0
Order By: Relevance
“…Thus, many authors [3]- [8] employ SimPoint [2], which defines application-specific simulation intervals, whereas other authors [9]- [12] choose to perform an initial fast forwarding or warm up of a determined number of instructions followed by a detailed simulation of a fixed number of subsequent instructions (both processes -forwarding and detailed simulation-are not application-specific and imply the same number of instructions for all evaluated benchmarks). This diversity also exists in the simulator employed (gem5 [13] in [4], [5], [7], [11], [14], Sniper [15] in [9], [16], or Scarab [17] in [6], [18], among others), the benchmarks used and the input data these applications receive (e.g., in the case of SPEC CPU suites, reference inputs in [3], [4], [7], [18], [19], test inputs in [16] or train inputs in [20]). Our motivational hypothesis in this work is that the particular simulation window employed when evaluating microarchitectural proposals related to the last level cache (LLC), such as cache replacement policies, can lead to incorrect conclusions.…”
Section: Introductionmentioning
confidence: 99%
“…Thus, many authors [3]- [8] employ SimPoint [2], which defines application-specific simulation intervals, whereas other authors [9]- [12] choose to perform an initial fast forwarding or warm up of a determined number of instructions followed by a detailed simulation of a fixed number of subsequent instructions (both processes -forwarding and detailed simulation-are not application-specific and imply the same number of instructions for all evaluated benchmarks). This diversity also exists in the simulator employed (gem5 [13] in [4], [5], [7], [11], [14], Sniper [15] in [9], [16], or Scarab [17] in [6], [18], among others), the benchmarks used and the input data these applications receive (e.g., in the case of SPEC CPU suites, reference inputs in [3], [4], [7], [18], [19], test inputs in [16] or train inputs in [20]). Our motivational hypothesis in this work is that the particular simulation window employed when evaluating microarchitectural proposals related to the last level cache (LLC), such as cache replacement policies, can lead to incorrect conclusions.…”
Section: Introductionmentioning
confidence: 99%
“…Intel introduced more efficient cache line flush instructions (e.g., clwb) to substitute the legacy clflush [23,29,68]. Cache line flush enables programmers to flush modified cache lines to the persistence domain, in which data can be deemed to be persistent upon a power outage [13,24,68,84]. The concept of persistence domain was initially linked to the feature of Asynchronous DRAM Refresh (ADR).…”
Section: Introductionmentioning
confidence: 99%