LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Oren Laadan <orenl@cs.columbia.edu>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org,
	containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-api@vger.kernel.org, tglx@linutronix.de,
	dave@linux.vnet.ibm.com, mingo@elte.hu, hpa@zytor.com,
	viro@zeniv.linux.org.uk
Subject: Re: [RFC v7][PATCH 2/9] General infrastructure for checkpoint restart
Date: Tue, 21 Oct 2008 22:55:13 -0400	[thread overview]
Message-ID: <20081022025513.GA7504@caradoc.them.org> (raw)
In-Reply-To: <48FE82DF.6030005@cs.columbia.edu>

On Tue, Oct 21, 2008 at 09:33:19PM -0400, Oren Laadan wrote:
> >> What happens if I pass it a pid of a process which I _do_ own, but it
> >> does not refer to a container's init process?
> > 
> > I would assume that do_checkpoint() would return -EINVAL, but it's a
> > great question:  Oren, did you have another plan?
> 
> Since we intentional provide minimal functionality to keep the patchset
> simple and allow easy review - we only checkpoint one task; it doesn't
> really matter because we don't deal with the entire container.
> 
> With the ability to checkpoint multiple process we will have to ensure
> that we checkpoint an entire container. I planned to return -EINVAL if
> the target task isn't a container init(1). Another option, if people
> prefer, is to use any task in a container to "represent" the entire
> container.

I haven't been following - but why this whole container restriction?
Checkpoint/restart of individual processes is very useful too.
There are issues with e.g. IPC, but I'm not convinced they're
substantially different than the issues already present for a
container.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2008-10-22  3:16 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20  5:40 [RFC v7][PATCH 0/9] Kernel based checkpoint/restart Oren Laadan
2008-10-20  5:40 ` [RFC v7][PATCH 1/9] Create syscalls: sys_checkpoint, sys_restart Oren Laadan
2008-10-20  5:40 ` [RFC v7][PATCH 2/9] General infrastructure for checkpoint restart Oren Laadan
2008-10-21 19:41   ` Andrew Morton
2008-10-21 20:24     ` Serge E. Hallyn
2008-10-21 20:41       ` Andrew Morton
2008-10-22  1:33       ` Oren Laadan
2008-10-22  2:55         ` Daniel Jacobowitz [this message]
2008-10-22  3:02           ` Dave Hansen
2008-10-22 14:29             ` Daniel Jacobowitz
2008-10-22 15:28         ` Serge E. Hallyn
2008-10-22 16:02           ` Oren Laadan
2008-10-22 17:03             ` Serge E. Hallyn
2008-10-22 18:32               ` Oren Laadan
2008-10-27  8:27             ` Peter Chubb
2008-10-27 11:03               ` Oren Laadan
2008-10-27 16:42                 ` Dave Hansen
2008-10-27 17:11                   ` Oren Laadan
2008-10-27 20:51                     ` Matt Helsley
2008-10-27 21:20                       ` Serge E. Hallyn
2008-10-27 21:51                       ` Oren Laadan
2008-10-27 22:09                         ` Dave Hansen
2008-10-28 18:33                           ` Serge E. Hallyn
2008-10-20  5:40 ` [RFC v7][PATCH 3/9] x86 support for checkpoint/restart Oren Laadan
2008-10-20  5:40 ` [RFC v7][PATCH 4/9] Dump memory address space Oren Laadan
2008-10-20  5:40 ` [RFC v7][PATCH 5/9] Restore " Oren Laadan
2008-10-20  5:40 ` [RFC v7][PATCH 6/9] Checkpoint/restart: initial documentation Oren Laadan
2008-10-28 16:48   ` Michael Kerrisk
2008-10-20  5:40 ` [RFC v7][PATCH 7/9] Infrastructure for shared objects Oren Laadan
2008-10-20  5:40 ` [RFC v7][PATCH 8/9] Dump open file descriptors Oren Laadan
2008-10-20  5:40 ` [RFC v7][PATCH 9/9] Restore open file descriprtors Oren Laadan
2008-10-21 19:21 ` [RFC v7][PATCH 0/9] Kernel based checkpoint/restart Andrew Morton
2008-10-21 20:41   ` Dave Hansen
2008-10-22  9:20     ` Ingo Molnar
2008-10-22 11:51       ` Daniel Lezcano

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=20081022025513.GA7504@caradoc.them.org \
    --to=dan@debian.org \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=hpa@zytor.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=orenl@cs.columbia.edu \
    --cc=serue@us.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --subject='Re: [RFC v7][PATCH 2/9] General infrastructure for checkpoint restart' \
    /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

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).