Differences

This shows you the differences between two versions of the page.

--- cluster:198 [2020/12/02 19:21] – hmeij07
+++ cluster:198 [2020/12/03 13:09] (current) – [GPU checkpoint/restart] hmeij07
@@ Line 12: / Line 12: @@
 An **excellent** in depth explanation can be found in this article
-  * [[https://arxiv.org/pdf/2008.10596.pdf|arXiv:2008.10596v1  [cs.DC]  24 Aug 2020CRAC: Checkpoint-Restart Architecture for CUDA with Streamsand UVM]]
+  * [[https://arxiv.org/pdf/2008.10596.pdf|CRAC: Checkpoint-Restart Architecture for CUDA with Streamsand UVM]]
-  * CRAC git site (notice early development): https://github.com/DMTCP-CRAC/CRAC-early-development
+  * git site (notice __early development__): https://github.com/DMTCP-CRAC/CRAC-early-development
-Some quotes from the article ...  //CRAC provides the ability to save and restore the state of CUDA by first using CUDA-specific save/restore operations, and then delegating to a traditional checkpoint-restart package.... In the end, the support of DMTCP for process virtualization and plugins makes it easier to add modular support for CUDA without having to excessively understand details of the internals of the host checkpointing package.//
+Some quotes from the article ...  //CRAC provides the ability to save and restore the state of CUDA by first using CUDA-specific save/restore operations, and then delegating to a traditional checkpoint-restart package.... In the end, the support of DMTCP for process virtualization and plugins makes it easier to add modular support for CUDA without having to excessively understand details of the internals of the host checkpointing package.//  This plugin will likely only work with recent gpu models.
-  * Slurm DMTCP inegration via plugin
+  * Slurm DMTCP integration with plugin
     * https://slurm.schedmd.com/SLUG16/ciemat-cr.pdf