public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oren Laadan <orenl@cs.columbia.edu>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: 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, 24 Apr 2008 19:13:01 -0400	[thread overview]
Message-ID: <481113FD.3010905@cs.columbia.edu> (raw)
In-Reply-To: <1209061809.12718.36.camel@nimitz.home.sr71.net>



Dave Hansen wrote:
> On Thu, 2008-04-24 at 11:00 +0400, Kirill Korotaev wrote:
>> Yeah... we talked with Andrew yesterday. He mostly agrees with a black
>> box.
>> He also said an interesting idea, that if you need compatibility
>> between the kernels (like we for example, support for migration from
>> 2.6.9 to 2.6.18 in OpenVZ)
>> you can do image conversion in user-space...
> 
> That sounds compelling to me.  I'm definitely willing to explore it.

Filtering/converting in user-space has long been part of zap: used to
be able to migrate between both minor and major versions of the kernel
(always upwards, of course).

In fact, I already proposed it as part of the original thread that led
eventually to the patch in question:
https://lists.linux-foundation.org/pipermail/containers/2008-February/009849.html

The need to be able to specify a desired ID (from user-space and/or from
in-kernel) remains.

Oren.

> Any thoughts on what we should start with?  What can we get merged, most
> easily?
> 
> -- Dave
> 
> _______________________________________________
> Containers mailing list
> Containers@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/containers

  reply	other threads:[~2008-04-24 23:23 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 [this message]
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
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=481113FD.3010905@cs.columbia.edu \
    --to=orenl@cs.columbia.edu \
    --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 \
    /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