FIRestarter: Practical Software Crash Recovery with Targeted Library-level Fault Injection

Bhat, Koustubha; Kouwe, Erik van der; Bos, Herbert; Giuffrida, Cristiano

doi:10.1109/dsn48987.2021.00048

Cited by 2 publications

(1 citation statement)

References 48 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We use a fault-injection test used in previous PM crash-consistency validation studies [13,31,96] to validate the correctness of crashconsistency. We design the fault-injection test as follows.…”

Section: Evaluation 71 Correctness and Soundnessmentioning

confidence: 99%

FFCCD

Solihin

et al. 2022

Proceedings of the 49th Annual International Symposium on Computer Architecture

View full text Add to dashboard Cite

Persistent Memory (PM) is increasingly supplementing or substituting DRAM as main memory. Prior work have focused on reusability and memory leaks of persistent memory but have not addressed a problem amplified by persistence, persistent memory fragmentation, which refers to the continuous worsening of fragmentation of persistent memory throughout its usage. This paper reveals the challenges and proposes the first systematic crash-consistent solution, Fence-Free Crash-consistent Concurrent Defragmentation (FFCCD). FFCCD resues persistent pointer format, root nodes and typed allocation provided by persistent memory programming model to enable concurrent defragmentation on PM. FFCCD introduces architecture support for concurrent defragmentation that enables a fence-free design and fast read barrier, reducing two major overheads of defragmenting persistent memory. The techniques is effective (28-73% fragmentation reduction) and fast (4.1% execution time overhead). CCS CONCEPTS• Hardware → Non-volatile memory; • Software and its engineering → Garbage collection.

show abstract

Section: Evaluation 71 Correctness and Soundnessmentioning

confidence: 99%