All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: xen-devel@lists.xensource.com
Cc: george.dunlap@eu.citrix.com, ian.jackson@eu.citrix.com
Subject: [PATCH 0 of 2] [Resend v2] remus: Checkpoint Compression
Date: Sat, 18 Jun 2011 21:32:18 -0700	[thread overview]
Message-ID: <patchbomb.1308457938@athos.nss.cs.ubc.ca> (raw)

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 :).

shriram

             reply	other threads:[~2011-06-19  4:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-19  4:32 Shriram Rajagopalan [this message]
2011-06-19  4:32 ` [PATCH 1 of 2] tools/libxc: Remus Checkpoint Compression Shriram Rajagopalan
2011-06-20 10:32   ` George Dunlap
2011-06-27 15:33   ` Ian Jackson
2011-06-27 17:22     ` Shriram Rajagopalan
2011-06-28 11:29       ` Ian Jackson
2011-06-19  4:32 ` [PATCH 2 of 2] remus: command line switche to enable/disable checkpoint compression Shriram Rajagopalan
2011-06-21 15:18 ` [PATCH 0 of 2] [Resend v2] remus: Checkpoint Compression Ian Jackson
2011-06-21 15:25   ` George Dunlap
2011-06-21 15:29     ` Ian Jackson
2011-06-21 16:17       ` Shriram Rajagopalan
2011-06-22  8:23 ` Ian Campbell
2011-06-22 16:47   ` Shriram Rajagopalan
2011-06-23 10:55     ` George Dunlap
2011-06-23 15:08       ` Shriram Rajagopalan

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=patchbomb.1308457938@athos.nss.cs.ubc.ca \
    --to=rshriram@cs.ubc.ca \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.