[RFC][PATCH 1/4] checkpoint-restart: general infrastructure
arnd at arndb.de
Fri Aug 8 15:39:19 PDT 2008
On Saturday 09 August 2008, Dave Hansen wrote:
> On Sat, 2008-08-09 at 00:13 +0200, Arnd Bergmann wrote:
> > Maybe you can invert the logic and let the new syscalls create a file
> > descriptor, and then have user space read or splice the checkpoint
> > data from it, and restore it by writing to the file descriptor.
> > It's probably easy to do using anon_inode_getfd() and would solve this
> > problem, but at the same time make checkpointing the current thread
> > hard if not impossible.
> Yeah, it does seem kinda backwards. But, instead of even having to
> worry about the anon_inode stuff, why don't we just put it in a fs like
> everything else? checkpointfs!
Well, anon_inodes are really easy to use and have replaced some of the
simple non-mountable file systems in the kernel.
checkpointfs sounds interesting and I guess in a plan9 world of fairies
and fantasy, you should be able to create a checkpoint of your system using
'tar czf - /proc/', but I'm not sure it helps here.
The main problem I see with that would be atomicity: If you want multiple
processes to keep interacting with each other, you need to save them at
the same point in time, which gets harder as you split your interface into
more than a single file descriptor.
More information about the Containers