All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: Linux-Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	Linux-Kernel
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Linux Checkpoint-Restart - v19
Date: Mon, 22 Feb 2010 18:17:00 -0500	[thread overview]
Message-ID: <4B83106C.7040203@cs.columbia.edu> (raw)

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

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

Thanks,

Application checkpoint/restart team

WARNING: multiple messages have this Message-ID (diff)
From: Oren Laadan <orenl@cs.columbia.edu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
	Linux-Containers <containers@lists.linux-foundation.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Linux Checkpoint-Restart - v19
Date: Mon, 22 Feb 2010 18:17:00 -0500	[thread overview]
Message-ID: <4B83106C.7040203@cs.columbia.edu> (raw)

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

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

Thanks,

Application checkpoint/restart team

             reply	other threads:[~2010-02-22 23:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 23:17 Oren Laadan [this message]
2010-02-22 23:17 ` Linux Checkpoint-Restart - v19 Oren Laadan
2010-03-01 21:36 ` Andrew Morton
     [not found]   ` <20100301133623.9808986f.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2010-03-01 22:56     ` Oren Laadan
2010-03-01 22:56   ` Oren Laadan
     [not found] ` <4B83106C.7040203-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-03-01 21:36   ` Andrew Morton
2010-03-15  8:55 ` Jiro SEKIBA
     [not found]   ` <a1c54a921003150155q4a0c7fc1vb02ba0464b07f452-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-15 22:55     ` Oren Laadan
2010-03-15 22:55   ` Oren Laadan
     [not found]     ` <4B9EBAF2.1060304-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-03-16  8:36       ` Jiro SEKIBA
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
     [not found]                 ` <FF5CB8EA-436D-4685-B7A2-946A83DF3F78-Xy3Dp9s2+bNGIRItUzBvX16hYfS7NtTn@public.gmane.org>
2010-03-24 16:47                   ` Serge E. Hallyn
     [not found]                     ` <20100324164758.GA21021-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-03-29  8:52                       ` Jiro SEKIBA
     [not found]                         ` <BC2CC354-59BA-465A-A863-0CDCD921A99A-Xy3Dp9s2+bNGIRItUzBvX16hYfS7NtTn@public.gmane.org>
2010-03-30  3:05                           ` Serge E. Hallyn
     [not found]                             ` <20100330030535.GA13362-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-03  9:03                               ` Jiro SEKIBA
     [not found]                                 ` <18557515-762E-4EE6-90D7-C8F782E487B2-Xy3Dp9s2+bNGIRItUzBvX16hYfS7NtTn@public.gmane.org>
2010-04-05 14:06                                   ` Serge E. Hallyn
     [not found]                                     ` <20100405140629.GG32049-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-05 14:31                                       ` Matt Helsley
     [not found]                                         ` <20100405143157.GX3345-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2010-04-06  2:54                                           ` Jiro SEKIBA
     [not found]                                             ` <39FCECBC-BFE3-4328-BCFC-CBACA3CB442E-Xy3Dp9s2+bNGIRItUzBvX16hYfS7NtTn@public.gmane.org>
2010-04-06 21:49                                               ` Nathan Lynch
2010-04-06 22:23                                                 ` Serge E. Hallyn
2010-04-07 13:08                                                 ` Jiro SEKIBA
     [not found]               ` <4BA39971.2080402-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-03-23 10:53                 ` Jiro SEKIBA
     [not found]             ` <EF179F3A-4FBA-4776-B7A4-48F5EF73DC9C-Xy3Dp9s2+bNGIRItUzBvX16hYfS7NtTn@public.gmane.org>
2010-03-19 15:34               ` Oren Laadan
     [not found]           ` <20100317205556.GA20750-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-03-19 13:14             ` Jiro SEKIBA
     [not found]         ` <0B4E8136-FFC6-490D-B04A-23A6E1A924FF-Xy3Dp9s2+bNGIRItUzBvX16hYfS7NtTn@public.gmane.org>
2010-03-17 20:55           ` Serge E. Hallyn

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=4B83106C.7040203@cs.columbia.edu \
    --to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
    --cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.