From: Cedric Le Goater <legoater@free.fr>
To: Oren Laadan <orenl@cs.columbia.edu>
Cc: containers@lists.osdl.org, linuxppc-dev@ozlabs.org,
Nathan Lynch <ntl@pobox.com>
Subject: Re: [PATCH 1/3] powerpc: bare minimum checkpoint/restart implementation
Date: Fri, 13 Mar 2009 16:42:20 +0100 [thread overview]
Message-ID: <49BA7EDC.1000705@free.fr> (raw)
In-Reply-To: <49B9D37A.1070503@cs.columbia.edu>
> More specifically, I envision restart to work like this:
>
> 1) user invokes user-land utility (e.g. "cr --restart ..."
> 2) 'cr' will create a new container
> 3) 'cr' will start a child in that container
process 1 in its private namespaces.
> 4) child will create rest of tree (in kernel or in user space - tbd)
> 5) each task in that tree will restore itself
> 6) 'cr' monitors this process
> 7) if all goes well - 'cr' report ok.
> 8) if something goes bad, 'cr' notices and notifies caller/user
that's MCR implementation of restart.
> so tasks that are restarting may just as well die badly - we don't care.
just sigkill them, but at end, before releasing the container from
a frozen state, we have to make sure the right number of tasks have
restarted ... so you need to track them along the way.
C.
next prev parent reply other threads:[~2009-03-13 15:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 22:41 [RFC/PATCH 0/3] checkpoint/restart for powerpc Nathan Lynch
2009-01-28 22:41 ` [PATCH 1/3] powerpc: bare minimum checkpoint/restart implementation Nathan Lynch
2009-01-29 6:41 ` Oren Laadan
2009-01-29 21:40 ` Nathan Lynch
2009-01-30 0:11 ` Oren Laadan
2009-01-30 20:25 ` Nathan Lynch
2009-02-17 7:03 ` Nathan Lynch
2009-02-17 20:02 ` [PATCH 1/3 v2] powerpc: heckpoint/restart implementation Nathan Lynch
2009-02-24 19:58 ` [PATCH 1/3] powerpc: bare minimum checkpoint/restart implementation Serge E. Hallyn
2009-02-24 21:11 ` Nathan Lynch
2009-03-13 3:36 ` Oren Laadan
2009-03-13 3:31 ` Oren Laadan
2009-03-13 15:42 ` Cedric Le Goater [this message]
2009-03-16 18:37 ` Nathan Lynch
2009-03-17 6:55 ` Cedric Le Goater
2009-03-18 9:15 ` Oren Laadan
2009-01-30 4:01 ` Serge E. Hallyn
2009-01-30 3:55 ` Serge E. Hallyn
2009-02-04 3:39 ` Benjamin Herrenschmidt
2009-02-04 15:54 ` Serge E. Hallyn
2009-02-04 20:58 ` Benjamin Herrenschmidt
2009-02-04 23:44 ` Oren Laadan
2009-02-05 0:16 ` Benjamin Herrenschmidt
2009-02-05 3:30 ` Oren Laadan
2009-02-05 16:09 ` Serge E. Hallyn
2009-02-05 21:01 ` Benjamin Herrenschmidt
2009-01-28 22:41 ` [PATCH 2/3] powerpc: wire up checkpoint and restart syscalls Nathan Lynch
2009-01-28 22:41 ` [PATCH 3/3] allow checkpoint/restart on powerpc Nathan Lynch
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=49BA7EDC.1000705@free.fr \
--to=legoater@free.fr \
--cc=containers@lists.osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
--cc=orenl@cs.columbia.edu \
/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;
as well as URLs for NNTP newsgroup(s).