public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
	Oren Laadan <orenl@cs.columbia.edu>,
	Kirill Korotaev <dev@parallels.com>,
	containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, Nadia.Derbey@bull.net,
	Andrew Morton <akpm@linux-foundation.org>,
	nick@nick-andrew.net, Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: Checkpoint/restart (was Re: [PATCH 0/4] - v2 - Object creation with a specified id)
Date: Thu, 10 Jul 2008 11:55:34 -0700	[thread overview]
Message-ID: <m163rd1sd5.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <20080710173246.GA1857@us.ibm.com> (Serge E. Hallyn's message of "Thu, 10 Jul 2008 12:32:46 -0500")

"Serge E. Hallyn" <serue@us.ibm.com> writes:

>> So, the checkpoint-as-a-corefile idea sounds good to me, but it
>> definitely leaves a lot of questions about exactly how we'll need to do
>> the restore.
>
> Talking with Dave over irc, I kind of liked the idea of creating a new
> fs/binfmt_cr.c that executes a checkpoint-as-a-coredump file.
>
> One thing I do not like about the checkpoint-as-coredump is that it begs
> us to dump all memory out into the file.  Our plan/hope was to save
> ourselves from writing out most memory by:
>
> 	1. associating a separate swapfile with each container
> 	2. doing a swapfile snapshot at each checkpoint
> 	3. dumping the pte entries (/proc/self/)
>
> If we do checkpoint-as-a-coredump, then we need userspace to coordinate
> a kernel-generated coredump with a user-generated (?) swapfile snapshot.
> But I guess we figure that out later.

Well it is a matter of which VMAs you dump.  For things that are file backed
you need to dump them.

I don't know that even a binfmt for per process level checkpoints is sufficient
but I do know having something of that granularity looks much easier.  Otherwise
it takes a bazillian little syscalls to do things no one else is interested in doing.

Eric

  reply	other threads:[~2008-07-10 19:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18  5:44 [PATCH 0/4] - v2 - Object creation with a specified id Nadia.Derbey
2008-04-18  5:45 ` [PATCH 1/4] - v2 - Provide a new procfs interface to set next id Nadia.Derbey
2008-04-18  5:45 ` [PATCH 2/4] - v2 - Provide a new procfs interface to set next upid nr(s) Nadia.Derbey
2008-04-18  5:45 ` [PATCH 3/4] - v2 - IPC: use the target ID specified in procfs Nadia.Derbey
2008-04-18  5:45 ` [PATCH 4/4] - v2 - PID: " Nadia.Derbey
2008-04-18 17:07 ` [PATCH 0/4] - v2 - Object creation with a specified id Dave Hansen
2008-04-21 11:32   ` Nadia Derbey
2008-04-22 19:36 ` Checkpoint/restart (was Re: [PATCH 0/4] - v2 - Object creation with a specified id) Alexey Dobriyan
2008-04-22 18:56   ` Dave Hansen
2008-04-22 19:51     ` Serge E. Hallyn
2008-04-22 21:01     ` Alexey Dobriyan
2008-04-22 22:56       ` Dave Hansen
2008-04-23  6:40         ` Kirill Korotaev
2008-04-23 15:33           ` Dave Hansen
2008-04-24  7:00             ` Kirill Korotaev
2008-04-24 18:30               ` Dave Hansen
2008-04-24 23:13                 ` Oren Laadan
2008-04-24  1:19           ` Oren Laadan
2008-07-10  1:58             ` Eric W. Biederman
2008-07-10 17:12               ` Dave Hansen
2008-07-10 17:32                 ` Serge E. Hallyn
2008-07-10 18:55                   ` Eric W. Biederman [this message]
2008-07-10 19:06                     ` Dave Hansen
2008-07-10 19:21                       ` Eric W. Biederman
2008-07-10 19:47                         ` Dave Hansen
2008-07-11  0:32                           ` Alexey Dobriyan
2008-07-17 23:19                           ` Oren Laadan
2008-07-17 23:16                   ` Oren Laadan
2008-07-18 16:18                     ` Serge E. Hallyn
2008-07-17 23:14                 ` Oren Laadan
2008-07-17 23:09               ` Oren Laadan
2008-04-23 14:23 ` [PATCH 0/4] - v2 - Object creation with a specified id Pavel Machek

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=m163rd1sd5.fsf@frodo.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=Nadia.Derbey@bull.net \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=dev@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@nick-andrew.net \
    --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