2018 IEEE 36th International Conference on Computer Design (ICCD) 2018
DOI: 10.1109/iccd.2018.00069
|View full text |Cite
|
Sign up to set email alerts
|

Breeze: User-Level Access to Non-Volatile Main Memories for Legacy Software

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
13
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
8
2

Relationship

1
9

Authors

Journals

citations
Cited by 17 publications
(13 citation statements)
references
References 32 publications
0
13
0
Order By: Relevance
“…Beyond individual data structures, several groups have developed systems to ensure the failure atomicity of lockbased critical sections [3,20,22,32] or speculative transactions [1,4,6,7,9,15,16,37,42,43,48,50]. Significantly, all of these systems ensure that an operation has persisted before permitting the calling thread to proceed-that is, they adopt the strict version of durable linearizability.…”
Section: Related Workmentioning
confidence: 99%
“…Beyond individual data structures, several groups have developed systems to ensure the failure atomicity of lockbased critical sections [3,20,22,32] or speculative transactions [1,4,6,7,9,15,16,37,42,43,48,50]. Significantly, all of these systems ensure that an operation has persisted before permitting the calling thread to proceed-that is, they adopt the strict version of durable linearizability.…”
Section: Related Workmentioning
confidence: 99%
“…First, WSP must be able to restore the entire system on failure recovery no matter how deep the volatile cache and memory hierarchy is as in off-chip DRAM cache as Optane's memory mode. Second, failure recovery should be offered to any programs (instead of being limited to in-memory databases and key-value stores) in a softwaretransparent manner, which is desired as a variety of recent works confirm that persistent programming is error-prone [20,[57][58][59][60][61]67].…”
Section: Motivationmentioning
confidence: 99%
“…This is not a fundamental limitation of Pronto or ASL, but it is necessary to support the easy conversion of volatile data structures into persistent data structures without compiler support. Previous work has shown how to ensure relocatability with a compiler [37]. Those techniques would apply to Pronto.…”
Section: Time Undo Loggingmentioning
confidence: 99%