From: Dave Hansen <dave@linux.vnet.ibm.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Oren Laadan <orenl@cs.columbia.edu>,
xemul@parallels.com, containers@lists.linux-foundation.org,
mingo@elte.hu, linux-kernel@vger.kernel.org, hch@infradead.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: "partial" container checkpoint
Date: Tue, 14 Apr 2009 09:37:03 -0700 [thread overview]
Message-ID: <1239727023.32604.69.camel@nimitz> (raw)
In-Reply-To: <20090414152951.GA7703@us.ibm.com>
On Tue, 2009-04-14 at 10:29 -0500, Serge E. Hallyn wrote:
> I think the perceived need for it comes, as above, from the pure
> checkpoint-a-whole-container-only view. So long as you will
> checkpoint/restore a whole container, then you'll end up doing
> something requiring privilege anyway. But that is not all of
> the use cases.
Yeah, there are certainly a lot of shades of gray here. I've been
talking to some HPC guys in the last couple of days. They certainly
have a need for checkpoint/restart, but much less of a need for doing
entire containers.
It also occurs to me that we have the potential to pull some
long-out-of-tree users back in. VMADump users, for instance:
http://bproc.sourceforge.net/c268.html
If we could do *just* a selective checkpoint of a single process's VMAs,
the bproc users could probably use sys_checkpoint() in some way. That's
*way* less than an entire container, but it would be really useful to
some people.
-- Dave
next prev parent reply other threads:[~2009-04-14 16:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 2:35 [PATCH 10/30] cr: core stuff Alexey Dobriyan
2009-04-10 9:35 ` Ingo Molnar
2009-04-10 11:43 ` Alexey Dobriyan
2009-04-10 16:19 ` Brian Haley
2009-04-13 8:10 ` Alexey Dobriyan
2009-04-13 21:47 ` Serge E. Hallyn
2009-04-14 5:52 ` Oren Laadan
2009-04-14 15:29 ` Serge E. Hallyn
2009-04-14 16:37 ` Dave Hansen [this message]
2009-04-14 17:30 ` "partial" container checkpoint Kevin Fox
2009-04-15 0:06 ` Paul Menage
2009-04-14 15:27 ` [PATCH 10/30] cr: core stuff Alexey Dobriyan
2009-04-14 15:41 ` Dave Hansen
2009-04-14 16:57 ` Alexey Dobriyan
2009-04-14 15:41 ` Serge E. Hallyn
2009-04-14 16:48 ` Dave Hansen
2009-04-14 17:00 ` Alexey Dobriyan
2009-04-14 17:04 ` Alexey Dobriyan
2009-04-14 17:23 ` checkpoint/restart: taking refcounts on kernel objects Dave Hansen
2009-05-01 12:56 ` Alexey Dobriyan
2009-04-14 17:43 ` [PATCH 10/30] cr: core stuff Oren Laadan
2009-04-14 5:22 ` Oren Laadan
2009-04-14 16:00 ` Alexey Dobriyan
2009-04-14 16:39 ` Dave Hansen
2009-04-14 17:28 ` Alexey Dobriyan
2009-04-14 18:19 ` Oren Laadan
2009-04-14 19:00 ` Alexey Dobriyan
2009-04-14 19:26 ` Oren Laadan
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=1239727023.32604.69.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=orenl@cs.columbia.edu \
--cc=serue@us.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=xemul@parallels.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