From: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [RFC][PATCH 0/2] CR: save/restore a single, simple task
Date: Wed, 30 Jul 2008 14:40:42 -0700 [thread overview]
Message-ID: <1217454042.26001.6.camel@nimitz> (raw)
In-Reply-To: <20080730213541.GA24192-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
On Wed, 2008-07-30 at 16:35 -0500, Serge E. Hallyn wrote:
> So task 5 created its mm_struct, task 6 is
> supposed to use the same mm_struct, so it finds that out from the
> context? I wonder whether that would start to become complicated
> when checkpointing nested containers.
It also doesn't fit well with the nsproxy idea. It would be very hard
to tell which nsproxies should be shared until the entire restart has
been completed and we've been able to figure out which ones are the
same.
This is just a coding/implementation issue, but I think it does reveal a
difference in ideology between these patches and the way that the kernel
works up until now. :)
-- Dave
next prev parent reply other threads:[~2008-07-30 21:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 3:24 [RFC][PATCH 0/2] CR: save/restore a single, simple task Oren Laadan
[not found] ` <Pine.LNX.4.64.0807292306570.9868-CXF6herHY6ykSYb+qCZC/1i27PF6R63G9nwVQlTi/Pw@public.gmane.org>
2008-07-30 21:35 ` Serge E. Hallyn
[not found] ` <20080730213541.GA24192-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-07-30 21:40 ` Dave Hansen [this message]
2008-07-31 0:37 ` Oren Laadan
2008-07-30 23:46 ` Oren Laadan
[not found] ` <4890FD57.7050601-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2008-07-31 11:23 ` Daniel Lezcano
[not found] ` <4891A0C4.5080906-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-07-31 15:25 ` Oren Laadan
[not found] ` <4891D962.3020407-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2008-07-31 17:15 ` Daniel Lezcano
2008-07-30 22:16 ` Serge E. Hallyn
2008-07-31 1:11 ` [Devel] " Andrey Mirkin
[not found] ` <200807310511.11648.major-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-07-31 21:28 ` Serge E. Hallyn
[not found] ` <20080731212810.GB7858-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-08-01 5:28 ` Andrey Mirkin
[not found] ` <200808010928.21220.major-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-08-21 21:37 ` Serge E. Hallyn
[not found] ` <20080821213724.GA17862-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-09-03 11:10 ` 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=1217454042.26001.6.camel@nimitz \
--to=dave-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.