From: Christopher Covington <cov-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>,
Saied Kazemi <saied-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
Tycho Andersen
<tycho.andersen-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: CRIU <criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [CRIU] CRIU @Plumbers
Date: Tue, 03 Feb 2015 11:10:20 -0500 [thread overview]
Message-ID: <54D0F2EC.4040702@codeaurora.org> (raw)
In-Reply-To: <54D0E216.3040007-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
On 02/03/2015 09:58 AM, Pavel Emelyanov wrote:
> On 02/02/2015 10:19 PM, Saied Kazemi wrote:
>> Given the wide spectrum of CRIU use cases, I am also in favor of organizing a
>> separate track for it.
>>
>> To that end, I can present and do a live demo of how CRIU was used to provide
>> native Docker container checkpoint and restore. This can be a full presentation
>> by itself or combined with another presentation.
>
> That's great :) I'll start filling the page with data soon then. Feel free to
> join and add the stuff you want.
>
>> A minor nit: for consistency, can we call it checkpoint/restore instead of checkpoint/restart?
>
> Google gives ~600k results for "checkpoint/restart" vs ~900k for "checkpoint/restore"
> so I don't mind :)
I prefer "restore" (perhaps a more migration focused term) myself, but I think
there is some history behind "restart" (perhaps a more fault tolerance focused
term) from at least the Berkeley Lab's Checkpoint/Restart project, which has
software releases from 2005 and papers from 2002.
http://crd.lbl.gov/departments/computer-science/CLaSS/research/BLCR/
http://crd.lbl.gov/departments/computer-science/CLaSS/research/BLCR/checkpoint-restart-publications/
Chris
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-02-03 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 10:05 CRIU @Plumbers Pavel Emelyanov
[not found] ` <54CF4BFF.8070505-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2015-02-02 16:58 ` [CRIU] " Serge Hallyn
2015-02-03 3:50 ` James Bottomley
[not found] ` <1422935454.2103.48.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2015-02-03 15:41 ` Serge E. Hallyn
[not found] ` <20150203154123.GB2923-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2015-02-03 15:52 ` James Bottomley
2015-02-02 17:06 ` Tycho Andersen
2015-02-02 19:19 ` Saied Kazemi
[not found] ` <CA+Um-gj1ynTwOsQNV7482Lz2GsCX+Leuz=QdSfPL1MVaF1CRGQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-03 14:58 ` Pavel Emelyanov
[not found] ` <54D0E216.3040007-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2015-02-03 16:10 ` Christopher Covington [this message]
[not found] ` <54D0F2EC.4040702-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-02-03 16:21 ` Saied Kazemi
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=54D0F2EC.4040702@codeaurora.org \
--to=cov-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=saied-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=tycho.andersen-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=xemul-bzQdu9zFT3WakBO8gow8eQ@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