[lkml]   [2008]   [Aug]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC][PATCH 0/4] kernel-based checkpoint restart

    Arnd Bergmann wrote:
    > On Friday 08 August 2008, Dave Hansen wrote:
    >> These patches are from Oren Laaden. I've refactored them
    >> a bit to make them a wee bit more reviewable. I think this
    >> separates out the per-arch bits pretty well. It should also
    >> be at least build-bisetable.
    > Cool stuff

    Thanks. This is a proof of concept so all sorts of feedback are
    definitely welcome. Some of the ideas and discussions are found
    and the notes:
    and the archives of the linux containers mailing list:
    (August and July).

    Several aspects of the implementation are still experimental and
    I expect them to evolve with the feedback. In particular, expect
    the specific user interface (syscalls) and the checkpoint image
    format to be moving targets.

    >> ============================== ckpt.c ================================
    >> #define _GNU_SOURCE /* or _BSD_SOURCE or _SVID_SOURCE */
    >> #include <stdio.h>
    >> #include <stdlib.h>
    >> #include <errno.h>
    >> #include <fcntl.h>
    >> #include <unistd.h>
    >> #include <asm/unistd_32.h>
    >> #include <sys/syscall.h>
    > Note that asm/unistd_32.h is not portable, you should use asm/unistd.h
    > in the example.
    >> pid_t pid = getpid();
    >> int ret;
    >> ret = syscall(__NR_checkpoint, pid, STDOUT_FILENO, 0);
    > Interface-wise, I would consider checkpointing yourself signficantly
    > different from checkpointing some other thread. If checkpointing
    > yourself is the common case, it probably makes sense to allow passing
    > of pid=0 for this.

    The checkpoint/restart code is meant to checkpoint a whole container,
    that is be able to save the state of multiple other tasks. The same
    code can also be used to checkpoint yourself fairly easily with minimal
    changes (see comments in the code about "in context" checkpoint/restart
    that take care of this).

    I suggest to keep the interface as is in the sense that the pid will
    identify the target container (e.g. the pid of the init process of that

    Then, pid=0 would mean "the container to which I belong" if
    you are inside a container (and therefore don't know the pid of the
    init process there).

    Finally, to checkpoint yourself, you would set the a bit in the flags
    argument to something like CR_CKPT_MYSELF. Such a flag will be needed
    internally anyway to special-case self checkpoint where appropriate.

    Comments are welcome.


     \ /
      Last update: 2008-08-08 21:53    [W:0.022 / U:34.576 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site