On 01/03/2012 05:34 PM, Orit Wasserman wrote:
Signed-off-by: Benoit Hudzia benoit.hud...@sap.com
Signed-off-by: Petter Svard pett...@cs.umu.se
Signed-off-by: Aidan Shribman aidan.shrib...@sap.com
Looks like the original authorship (From: ) and signoffs were lost in
the actual patches.
--
On 01/04/2012 03:02 PM, Avi Kivity wrote:
On 01/03/2012 05:34 PM, Orit Wasserman wrote:
Signed-off-by: Benoit Hudzia benoit.hud...@sap.com
Signed-off-by: Petter Svard pett...@cs.umu.se
Signed-off-by: Aidan Shribman aidan.shrib...@sap.com
Looks like the original authorship (From: ) and
Changes from v4:
1) Rebase
2) divide patch into 9 patches
3) move memory allocation into cache_insert
By using XBZRLE (Xor Binary Zero Run-Length-Encoding) we can reduce VM downtime
and total live-migration time of VMs running memory write intensive workloads
typical of large enterprise
On 01/03/2012 09:34 AM, Orit Wasserman wrote:
Changes from v4:
1) Rebase
2) divide patch into 9 patches
3) move memory allocation into cache_insert
By using XBZRLE (Xor Binary Zero Run-Length-Encoding) we can reduce VM downtime
and total live-migration time of VMs running memory write intensive
On 01/03/2012 06:32 PM, Anthony Liguori wrote:
On 01/03/2012 09:34 AM, Orit Wasserman wrote:
Changes from v4:
1) Rebase
2) divide patch into 9 patches
3) move memory allocation into cache_insert
By using XBZRLE (Xor Binary Zero Run-Length-Encoding) we can reduce VM
downtime
and total
Changes from v4:
1) Rebase
2) divide patch into 9 patches
3) move memory allocation into cache_insert
By using XBZRLE (Xor Binary Zero Run-Length-Encoding) we can reduce VM downtime
and total live-migration time of VMs running memory write intensive workloads
typical of large enterprise
