From: Andrew Morton <akpm@linux-foundation.org>
To: Oren Laadan <orenl@cs.columbia.edu>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
Linux-Containers <containers@lists.linux-foundation.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux Checkpoint-Restart - v19
Date: Mon, 1 Mar 2010 13:36:23 -0800 [thread overview]
Message-ID: <20100301133623.9808986f.akpm@linux-foundation.org> (raw)
In-Reply-To: <4B83106C.7040203@cs.columbia.edu>
On Mon, 22 Feb 2010 18:17:00 -0500
Oren Laadan <orenl@cs.columbia.edu> wrote:
> Hi Andrew,
>
> We've put a stake in the ground for our next set of checkpoint/restart
> patches, v19. It has some great new stuff, and we put extra effort to
> address your concerns. We would like to have the code included in -mm
> for wider feedback and testing.
>
> This one is able to checkpoint/restart screen and vnc sessions, and
> live-migrate network servers between hosts. It also adds support for
> x86-64 (in addition to x86-32, s390x and powerpc). It is rebased to
> kernel 2.6.33-rc8.
>
> Since one of your main concerns was about what is not yet implemented
> and how complicated or ugly it will be to support that, we've put up
> a wiki page to address that. In it there is a simple table that lists
> what is not implemented and the anticipated solution impact, and for
> some entries a link to more details.
>
> The page is here: http://ckpt.wiki.kernel.org/index.php/Checklist
Does "Refuses to Checkpoint" mean that an attempt to checkpoint will
fail, return the failure to userspace and the system continues as
before?
> We want to stress that the patchset is already very useful as-is. We
> will keep working to implement more features cleanly. Some features we
> are working on include network namespaces and device configurations,
> mounts and mounts namespaces, and file locks. Should a complicated
> feature prove hard to implement, users have alternatives systems like
> kvm, until we manage to come up with a clean solution.
>
> We believe that maintenance is best addressed through testing. We now
> have a comprehensive test-suite to automatically find regressions.
> In addition, we ran LTP and the results are the same with CHECKPOINT=n
> and =y.
>
> If desired we'll send the whole patchset to lkml, but the git trees
> can be seen at:
>
> kernel: http://www.linux-cr.org/git/?p=linux-cr.git;a=summary
> user tools: http://www.linux-cr.org/git/?p=user-cr.git;a=summary
> tests suite: http://www.linux-cr.org/git/?p=tests-cr.git;a=summary
>
I'd suggest waiting until very shortly after 2.6.34-rc1 then please
send all the patches onto the list and let's get to work.
next prev parent reply other threads:[~2010-03-01 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 23:17 Linux Checkpoint-Restart - v19 Oren Laadan
2010-03-01 21:36 ` Andrew Morton [this message]
2010-03-01 22:56 ` Oren Laadan
2010-03-15 8:55 ` Jiro SEKIBA
2010-03-15 22:55 ` Oren Laadan
2010-03-16 8:36 ` Jiro SEKIBA
2010-03-17 20:55 ` Serge E. Hallyn
2010-03-19 13:14 ` Jiro SEKIBA
2010-03-19 15:34 ` Oren Laadan
2010-03-23 10:53 ` Jiro SEKIBA
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100301133623.9808986f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orenl@cs.columbia.edu \
--cc=serue@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox