2008
DOI: 10.1007/978-3-540-85261-2_1
|View full text |Cite
|
Sign up to set email alerts
|

Compiler-Enhanced Incremental Checkpointing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
14
0

Year Published

2009
2009
2014
2014

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 10 publications
(14 citation statements)
references
References 4 publications
0
14
0
Order By: Relevance
“…This process restores the memory changes captured in the checkpointing buffer. Upon completion of the checkpointing recovery, the program resumes its normal Prior research has investigated hardware-based checkpointing [5,31,46] and software-only checkpointing [11,12,35,39,50,62]. Hardware-based schemes rely on hardware support to buffer checkpointing states and facilitate recovery.…”
Section: Checkpointing Basicsmentioning
confidence: 99%
See 2 more Smart Citations
“…This process restores the memory changes captured in the checkpointing buffer. Upon completion of the checkpointing recovery, the program resumes its normal Prior research has investigated hardware-based checkpointing [5,31,46] and software-only checkpointing [11,12,35,39,50,62]. Hardware-based schemes rely on hardware support to buffer checkpointing states and facilitate recovery.…”
Section: Checkpointing Basicsmentioning
confidence: 99%
“…However, existing software-only checkpointing schemes suffer from prohibitive overhead by copying a large amount of memory at runtime. These schemes often employ heavy-weight checkpointing processes that operate at the application level [11,12], operating system level [34,39,50] or virtual-machine level [62]. They focus on providing software checkpointing service to enhance system robustness and reliability, thus performance of checkpoint-enabled applications is not the primary concern.…”
Section: Checkpointing Basicsmentioning
confidence: 99%
See 1 more Smart Citation
“…With MemCheckPoint stores are not commit points and memory can be corrupted with wrong values. Thus, a mechanism for memory checkpointing either in software [4] or in hardware, such as ReVive [24] …”
Section: Knobsmentioning
confidence: 99%
“…Another effort to tackle the non-FIFO is Message Tagging [4,18]. The idea behind Message Tagging is that the system wraps some additional information onto the outgoing messages, which is called header.…”
Section: Chandy-lamport Algorithmmentioning
confidence: 99%