Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Cc: Linux Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: ckpt-v20-dev, ckpt-v21-rc1
Date: Wed, 31 Mar 2010 12:33:39 -0500	[thread overview]
Message-ID: <20100331173339.GA19371@us.ibm.com> (raw)
In-Reply-To: <4BB1997B.1010901-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>

Quoting Oren Laadan (orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org):
> 
> I pulled all the recent patches in linux-cr (except for ipv6 fixup
> set), and created the following two branches:
> 
> ckpt-v20-dev - patches applied onto pof v20
> ckpt-v21-rc1 - patches folded into a clean patchset
> 
> Likewise with user-cr (but with more exceptions - working now on
> pulling more patches in).
> 
> This is totally untested except for successful compilation...
> 
> Oren.

v21 with the recent patches applied seems rock-solid to me, on
x86-64, s390x, and powerpc.

recent patches means:
	skip down interfaces v2,
	put fops->checkpoint under ifdef
	get rid of ckpt_hdr_vpids,
	export net checkpoint fns

for kernel and

	Add --nonetns switch to user-cr checkpoint
	fix vpids
	user-c/r: get rid of ckpt_hdr_vpids

to user-cr#ckpt-v20-dev

Do we want to try and incorporate Matt's patchset to clear out
linux-2.6/checkpoint/ next, or ship what we have?

-serge

  parent reply	other threads:[~2010-03-31 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30  6:26 ckpt-v20-dev, ckpt-v21-rc1 Oren Laadan
     [not found] ` <4BB1997B.1010901-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-03-30 20:56   ` Serge E. Hallyn
2010-03-31 17:33   ` Serge E. Hallyn [this message]
     [not found]     ` <20100331173339.GA19371-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-01  5:31       ` Oren Laadan
     [not found]         ` <4BB42FBB.8030206-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-04-01 14:17           ` Serge E. Hallyn
     [not found]             ` <20100401141740.GB22648-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-01 18:09               ` Nathan Lynch
2010-04-01 18:54                 ` Nathan Lynch
2010-04-01 19:10                   ` Serge E. Hallyn
     [not found]                     ` <20100401191001.GA8882-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-01 20:57                       ` Nathan Lynch
2010-04-01 21:15           ` Matt Helsley

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=20100331173339.GA19371@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=orenl-eQaUEPhvms7ENvBUuze7eA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox