public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Andrey Mirkin <major@openvz.org>
Cc: Oren Laadan <orenl@cs.columbia.edu>,
	"Serge E. Hallyn" <serue@us.ibm.com>,
	Cedric Le Goater <clg@fr.ibm.com>,
	Daniel Lezcano <dlezcano@fr.ibm.com>,
	Louis Rilling <Louis.Rilling@kerlabs.com>,
	containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Devel] Re: [PATCH 0/9] OpenVZ kernel based checkpointing/restart
Date: Thu, 30 Oct 2008 10:03:35 -0700	[thread overview]
Message-ID: <1225386215.12673.280.camel@nimitz> (raw)
In-Reply-To: <200810300902.47067.major@openvz.org>

On Thu, 2008-10-30 at 10:02 +0400, Andrey Mirkin wrote:
> Anyway we should ask everyone what they think about user- and kernel- based 
> process creation.
> Dave, Serge, Cedric, Daniel, Louis what do you think about that?

My worry is where a single sys_restart() plus in-kernel process creation
takes us.

In practice, what do we do?  Do we single-thread the entire restore
process?  Or, do we do in-kernel process creation and have multiple
kernel threads trying to read out of different points in the checkpoint
file, trying to restore all their own states in parallel?  Does that
mean that we can't in practice restore from a fd like a pipe or a
network socket?

In the same way, if we *do* create the processes in userspace, how do we
do _that_?  Do we just fork() and sleep() until the kernel comes along
and blows our state away?  How does the kernel process doing the
restoring tell userspace how many things to fork?  How do we match these
new userspace processes up with the ones coming out of the checkpoint
process?

To me, it's just way too early to talk about this stuff.  Both
approaches have their issues, and I'm yet to see the differences
manifested in code so I can really sink my teeth into them

-- Dave


  parent reply	other threads:[~2008-10-30 17:04 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 10:57 [PATCH 0/9] OpenVZ kernel based checkpointing/restart Andrey Mirkin
2008-09-03 10:57 ` [PATCH 1/9] Introduce trivial sys_checkpoint and sys_restore system calls Andrey Mirkin
2008-09-03 10:57   ` [PATCH 2/9] Make checkpoint/restart functionality modular Andrey Mirkin
2008-09-03 10:57     ` [PATCH 3/9] Introduce context structure needed during checkpointing/restart Andrey Mirkin
2008-09-03 10:57       ` [PATCH 4/9] Introduce container dump function Andrey Mirkin
2008-09-03 10:57         ` [PATCH 5/9] Introduce function to dump process Andrey Mirkin
2008-09-03 10:57           ` [PATCH 6/9] Introduce functions to dump mm Andrey Mirkin
2008-09-03 10:57             ` [PATCH 7/9] Introduce function for restarting a container Andrey Mirkin
2008-09-03 10:57               ` [PATCH 8/9] Introduce functions to restart a process Andrey Mirkin
2008-09-03 10:57                 ` [PATCH 9/9] Introduce functions to restore mm Andrey Mirkin
2008-09-03 14:32                 ` [PATCH 8/9] Introduce functions to restart a process Louis Rilling
2008-09-13 17:34                   ` Pavel Machek
2008-09-03 14:17             ` [PATCH 6/9] Introduce functions to dump mm Louis Rilling
2008-09-03 14:23         ` [PATCH 4/9] Introduce container dump function Serge E. Hallyn
2008-09-03 14:45           ` Andrey Mirkin
2008-09-03 12:29       ` [PATCH 3/9] Introduce context structure needed during checkpointing/restart Matthieu Fertré
2008-09-03 14:11         ` Andrey Mirkin
2008-09-03 13:56       ` Louis Rilling
2008-09-03 14:07         ` Andrey Mirkin
2008-09-03 14:13       ` Cedric Le Goater
2008-09-03 14:29         ` Andrey Mirkin
2008-09-03 14:27     ` [PATCH 2/9] Make checkpoint/restart functionality modular Serge E. Hallyn
2008-09-03 14:51       ` Andrey Mirkin
2008-09-03 11:44   ` [PATCH 1/9] Introduce trivial sys_checkpoint and sys_restore system calls Cedric Le Goater
2008-09-03 13:05     ` [Devel] " Andrey Mirkin
2008-09-03 12:28 ` [PATCH 0/9] OpenVZ kernel based checkpointing/restart Cedric Le Goater
2008-09-03 13:59   ` [Devel] " Andrey Mirkin
2008-09-04 22:55     ` Dave Hansen
2008-09-03 14:18   ` Serge E. Hallyn
2008-09-03 13:49 ` Louis Rilling
2008-09-03 14:06   ` Louis Rilling
2008-09-03 14:19     ` Andrey Mirkin
2008-09-03 14:26     ` Cedric Le Goater
2008-09-03 14:53       ` Andrey Mirkin
2008-09-04  8:14 ` Oren Laadan
2008-09-04 14:05 ` Dave Hansen
2008-10-17 23:33 ` Dave Hansen
2008-10-20 11:10   ` Louis Rilling
2008-10-20 13:25     ` Daniel Lezcano
2008-10-20 13:48       ` Cedric Le Goater
2008-10-20 13:49         ` Daniel Lezcano
2008-10-20 15:53       ` Oren Laadan
2008-10-20 16:37         ` Daniel Lezcano
2008-10-20 17:23           ` Serge E. Hallyn
2008-10-21  0:18             ` Oren Laadan
2008-10-21  0:58               ` Serge E. Hallyn
2008-10-21 13:24               ` Daniel Lezcano
2008-10-27 14:45           ` [Devel] " Andrey Mirkin
2008-10-20 16:51         ` Serge E. Hallyn
2008-10-21  9:36         ` Cedric Le Goater
2008-10-20 16:36     ` Dave Hansen
2008-10-20 12:14   ` [Devel] " Andrey Mirkin
2008-10-20 15:55     ` Dave Hansen
2008-10-27 14:07       ` Andrey Mirkin
2008-10-27 14:39         ` Oren Laadan
2008-10-30  6:02           ` Andrey Mirkin
2008-10-30 11:47             ` Louis Rilling
2008-10-30 17:08               ` Dave Hansen
2008-10-30 18:01                 ` Louis Rilling
2008-10-30 18:28                   ` Oren Laadan
2008-10-30 17:45               ` Oren Laadan
2008-10-30 18:14                 ` Louis Rilling
2008-10-30 18:32                   ` Oren Laadan
2008-10-31 10:37                     ` Louis Rilling
2008-10-30 14:08             ` Serge E. Hallyn
2008-10-30 17:03             ` Dave Hansen [this message]
2008-11-03 19:35         ` Oren Laadan
2008-10-20 17:17     ` Oren Laadan
2008-10-27 14:38       ` Andrey Mirkin

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=1225386215.12673.280.camel@nimitz \
    --to=dave@linux.vnet.ibm.com \
    --cc=Louis.Rilling@kerlabs.com \
    --cc=clg@fr.ibm.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=dlezcano@fr.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=major@openvz.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