| |||||||||||||
this is one process at a timethis is one process at a timePosted Aug 15, 2008 6:59 UTC (Fri) by dlang (✭ supporter ✭, #313)In reply to: Out-of-tree project has been doing checkpointing and restore for some time by dowdle Parent article: Kernel-based checkpoint and restart
for everyone pointing at virutaliztion, hibernation, etc, this allows you to just checkpoint and restore just a single process. you don't have to save the entire system if this can be made to work reliably on one system it can group (with the help of namespaces) the ability to take the image and resume it on a different system.
(Log in to post comments)
this is one process at a time Posted Aug 16, 2008 3:48 UTC (Sat) by kolyshkin (subscriber, #34342) [Link] Actually there's no way to checkpoint a single process, just because it has lots of relations with other processes. Starting from parent-child relationship (a process is at least someone's child and the parent do not expect a child to "disappear" suddenly), down to inter-process communication such as inter-process pipes etc., a process just can't be torn apart from its neighbourhood and be checkpointed. That is why containers are a prerequisite to checkpointing. A container is a self-sustained process group not tied to any other processes, and thus it can be checkpointed. It's interesting that some people think a container is just a thing needed for checkpointing, while others think of checkpointing as just yet another feature of containers.
|
|||||||||||||