This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [PATCH 0 of 2] [Resend v2] remus: Checkpoint Compression

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH 0 of 2] [Resend v2] remus: Checkpoint Compression
From: Shriram Rajagopalan <rshriram@xxxxxxxxx>
Date: Sat, 18 Jun 2011 21:32:18 -0700
Cc: george.dunlap@xxxxxxxxxxxxx, ian.jackson@xxxxxxxxxxxxx
Delivery-date: Sat, 18 Jun 2011 21:40:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mercurial-patchbomb/1.4.3
This patch series adds checkpoint compression functionality to Remus.

Modifications since the first version:
1. As George pointed out, signalling the receiver to enable compression
logic is done through XC_SAVE_ID_ENABLE_COMPRESSION marker, instead of
sending the compression flag as a separate entity. This way, live migration
compatibility is maintained with target machines running older
versions of xen.

2. Added comments at appropriate places to explain the compression
control logic in xc_domain_save/restore.

3. Tended to nitpicks :).


Xen-devel mailing list