From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
ccr-Gr7syQlKEaBFgBK04Mzu/R2eb7JE58TQ@public.gmane.org,
Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
Subject: Re: Checkpoint/Restart mini-summit
Date: Wed, 16 Jul 2008 21:27:29 -0500 [thread overview]
Message-ID: <20080717022729.GC21726@us.ibm.com> (raw)
In-Reply-To: <m1sku9zfhc.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
Quoting Eric W. Biederman (ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org):
> "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> writes:
>
> > Quoting Eric W. Biederman (ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org):
> >> "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> writes:
> >>
> >> > Right, the whole point of Daniel including a 'reading list' was just so
> >> > that we can avoid wasting time discussing existing implementations. So
> >> > he wasn't suggesting that we would be discussing those in detail, in
> >> > fact quite the opposite.
> >>
> >> Right however he was suggesting we discuss how to implement it without
> >> agreeing on basic principles. Maybe I'm wrong and all of the different
> >> development groups have a common idea of what needs to be done but
> >> I would be surprised if that were the case.
> >
> > IMO recent threads have clearly proven that you're right about basic
> > principles. Question is what is the right level to start at first, and
> > how do we go about reaching concensus? I.e. is the first question
> > whether we should do a fully in-kernel checkpoint and restart vs
> > entirely userspace vs a mix, or is there another place we should start?
>
> Where all good kernel features start. With the necessary mechanisms in
> the kernel and the policy in user space.
>
> If we want to replay all of the user space actions to create the
> environment at the time of the checkpoint we already have all of the
> kernel support we need as the applications go to their current state
> using current system calls.
>
> I think we want something a bit more efficient.
>
> > It sounds like you have some good ideas in any case on where to start so
> > I'm glad you'll be there :)
>
>
> Will we have a white board or a large piece paper or something we can draw
> on and talk about?
>
> Eric
Hi C.,
I'm sorry after all the emails I'm not straight on what we're actually
getting. We have a U-shaped room, but do we have a blackboard or
whiteboard? Is there a speakerphone? Wireless or at least wired
internet?
thanks,
-serge
next prev parent reply other threads:[~2008-07-17 2:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 10:49 Checkpoint/Restart mini-summit Daniel Lezcano
[not found] ` <487C80C9.2040105-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-07-15 18:44 ` Eric W. Biederman
[not found] ` <m1prpfc7hj.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-07-16 15:15 ` Serge E. Hallyn
[not found] ` <20080716151530.GA26496-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-07-16 19:04 ` Eric W. Biederman
[not found] ` <m18ww14pm7.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-07-16 19:35 ` Serge E. Hallyn
[not found] ` <20080716193538.GA28393-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-07-16 21:27 ` Eric W. Biederman
[not found] ` <m1sku9zfhc.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-07-17 2:27 ` Serge E. Hallyn [this message]
[not found] ` <20080717022729.GC21726-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-07-17 3:02 ` C. Craig Ross
2008-07-17 16:15 ` Daniel Lezcano
2008-07-15 18:54 ` Eric W. Biederman
[not found] ` <m1lk03c71k.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-07-16 15:17 ` Serge E. Hallyn
[not found] ` <20080716151707.GB26496-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-07-16 15:26 ` 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=20080717022729.GC21726@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=ccr-Gr7syQlKEaBFgBK04Mzu/R2eb7JE58TQ@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox