L.M. Silva and J.G. Silva. System-level versus User-defined Checkpointing. In Seventeenth Symposium on Reliable Distributed Systems, Oct. 1998. Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
An Application-Transparent, Platform-Independent.. - Gendelman, Bic.. (2000) (2 citations) (Correct)
....preprocessor to insert extra statements into the code, to save the program counter and the stack. This approach has some limitations: the user is responsible for saving C variables that are in the scope at the time of a checkpoint. A checkpointing library was developed by Silva, Veer, and Silva [20]. In their approach the user is responsible for specifying the data that has to be included into checkpoints. The resulting checkpoints are architecture independent. Another approach to checkpointing was implemented in the Charm system [21] Charm is an object oriented parallel language based ....
.... TransParency Checkpoint Portability Application Support System Support Consistent system state Examples Applicationbased Yes No Yes All the work None Captured by application [24] Run time library Yes No Yes When and what to checkpoint Checkpointing routines Ensured by checkpoint placement [20,25,26] Compilerbased Yes Almost Yes When to checkpoint None Not implemented [19,22,23, 27, 28] Environmentbased Yes Yes Yes Optional Checkpointing supported by the environment Captured by the environment [19,21] this work System based No Yes No Optional All Not implemented [3,11] Figure 16 14 There ....
Luis M. Silva, Joao G Silva. System-level versus User-Defined Checkpointing , Symposium on Fault-Tolerant Computing, pp 68-74, 1998
An Adaptive Checkpointing Protocol to Bound Recovery Time.. - Ssu, Yao, Fuchs (1999) (1 citation) (Correct)
....is almost transparent but may interfere with debugging. Checkpoint insertion by application users relies on manually placing checkpoints in the most suitable locations (e.g. where the checkpoint size is the smallest) or excluding unnecessary process states to achieve low checkpoint overhead [22, 36]. Strategies for initiating checkpoints can also be classified by the following three categories: Static: Checkpointing is initiated whenever the application reaches pre specified locations. This approach is not explicitly based on time. The locations for checkpointing may be defined by ....
L. M. Silva and J. G. Silva, "System-Level versus User-Defined Checkpointing," Proceedings of IEEE Reliable Distributed Systems Symposium, pp. 68--74, Oct. 1998.
Checkpoint and Restart for Distributed Components in XCAT3 - Sriram Krishnan Dennis (2004) (Correct)
No context found.
L.M. Silva and J.G. Silva. System-level versus User-defined Checkpointing. In Seventeenth Symposium on Reliable Distributed Systems, Oct. 1998.
Duplex: A Reusable Fault Tolerance Extension.. - Sharma, Chen, Li.. (2003) (3 citations) (Correct)
No context found.
L.M. Silva and J.G. Silva. System-level versus user-defined checkpointing. In Symposium on Reliable Distributed Systems, West Lafayette, IN, pages 68--74, Oct. 1998.
A Survey of Rollback-Recovery Protocols in.. - Elnozahy, Alvisi.. (1996) (161 citations) (Correct)
No context found.
L.M. Silva and J.G. Silva. "System-level versus user-defined checkpointing." In Proceedings of the Seventeenth Symposium on Reliable Distributed Systems, pp. 68---74, Oct. 1998.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC