Difference between revisions of "GPU Checkpointing"
Jump to navigation
Jump to search
m |
m |
||
| Line 1: | Line 1: | ||
| − | This page explains how CRIU handles GPU-accelerated workloads, what vendor components are needed (NVIDIA & AMD), and how to use them for processes and containers. For more information, check out the [https://arxiv.org/abs/2502.16631 CRIUgpu paper | + | This page explains how CRIU handles GPU-accelerated workloads, what vendor components are needed (NVIDIA & AMD), and how to use them for processes and containers. For more information, check out the [https://arxiv.org/abs/2502.16631 CRIUgpu paper]. |
== How CRIU integrates with GPU checkpointing mechanisms? == | == How CRIU integrates with GPU checkpointing mechanisms? == | ||
Revision as of 18:17, 29 October 2025
This page explains how CRIU handles GPU-accelerated workloads, what vendor components are needed (NVIDIA & AMD), and how to use them for processes and containers. For more information, check out the CRIUgpu paper.
How CRIU integrates with GPU checkpointing mechanisms?
CRIU checkpoints Linux-kernel resources (e.g., memory, threads, files, sockets). GPU state such as device memory, contexts, and queues that lives outside normal process address space needs special handling, so CRIU relies on vendor-specific plugins.
CUDA Plugin
The checkpointing functionality for CUDA applications is enabled through a command-line utility called cuda-checkpoint. This utility allows to transparently checkpoint and restore the GPU state of a running Linux process.