All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
To: Linux Kernel Mailing List
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	CRIU <criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Subject: [Announce] Checkpoint-restore tool v0.5
Date: Tue, 30 Apr 2013 21:30:55 +0400	[thread overview]
Message-ID: <517FFFCF.4080301@parallels.com> (raw)

Ladies and Gentlemen,

I'm glad to announce the 5th release of the checkpoint-restore tool!

This release is mostly about the tool itself. The v3.9 kernel, with which the
new CRIU tool should be used, only contains a couple of bug fixes related to
the C/R project and no new related features. As for the tool itself, there's
a lot of bugs fixed, thanks to new users that come to try the CRIU tool :)

The biggest "new-feature" change so far is about dumping the applications memory.
We have two enhancements in this area:

* memory dumps can be directly sent to the remote node, to speed live migration up;

and

* with the custom crkernel (patches are expected to get merged in Linux-3.10) one
  can track the memory changes, which in turn allows to do e.g. incremental dumps
  or optimize the live migration by sending memory to remote host before freezing
  the application.

The full list of changes is here: http://criu.org/Download/criu/0.5

Have fun!

Thanks,
Pavel

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Emelyanov <xemul@parallels.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Containers <containers@lists.linux-foundation.org>,
	CRIU <criu@openvz.org>
Subject: [Announce] Checkpoint-restore tool v0.5
Date: Tue, 30 Apr 2013 21:30:55 +0400	[thread overview]
Message-ID: <517FFFCF.4080301@parallels.com> (raw)

Ladies and Gentlemen,

I'm glad to announce the 5th release of the checkpoint-restore tool!

This release is mostly about the tool itself. The v3.9 kernel, with which the
new CRIU tool should be used, only contains a couple of bug fixes related to
the C/R project and no new related features. As for the tool itself, there's
a lot of bugs fixed, thanks to new users that come to try the CRIU tool :)

The biggest "new-feature" change so far is about dumping the applications memory.
We have two enhancements in this area:

* memory dumps can be directly sent to the remote node, to speed live migration up;

and

* with the custom crkernel (patches are expected to get merged in Linux-3.10) one
  can track the memory changes, which in turn allows to do e.g. incremental dumps
  or optimize the live migration by sending memory to remote host before freezing
  the application.

The full list of changes is here: http://criu.org/Download/criu/0.5

Have fun!

Thanks,
Pavel

             reply	other threads:[~2013-04-30 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30 17:30 Pavel Emelyanov [this message]
2013-04-30 17:30 ` [Announce] Checkpoint-restore tool v0.5 Pavel Emelyanov

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=517FFFCF.4080301@parallels.com \
    --to=xemul-bzqdu9zft3wakbo8gow8eq@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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.