[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH Remus v2 01/10] tools/libxc: adjust the memory allocation for migration

To: Yang Hongyang <yanghy@xxxxxxxxxxxxxx>
From: Ian Campbell <ian.campbell@xxxxxxxxxx>
Date: Mon, 11 May 2015 12:50:39 +0100
Cc: wei.liu2@xxxxxxxxxx, eddie.dong@xxxxxxxxx, wency@xxxxxxxxxxxxxx, andrew.cooper3@xxxxxxxxxx, yunhong.jiang@xxxxxxxxx, ian.jackson@xxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxx, rshriram@xxxxxxxxx
Delivery-date: Mon, 11 May 2015 11:50:45 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Fri, 2015-05-08 at 17:33 +0800, Yang Hongyang wrote:
> Move the memory allocation before the concrete live/nolive save
> in order to avoid the free/alloc memory loop when using Remus.
> Rename the to_send bitmap to dirty_bitmap.

Doing the rename in a precursor patch would make the functional change
much easier to see.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH Remus v2 01/10] tools/libxc: adjust the memory allocation for migration
  - From: Hongyang Yang

References:
- [Xen-devel] [PATCH Remus v2 00/10] Remus support for Migration-v2
  - From: Yang Hongyang
- [Xen-devel] [PATCH Remus v2 01/10] tools/libxc: adjust the memory allocation for migration
  - From: Yang Hongyang

Prev by Date: Re: [Xen-devel] [PATCH Remus v2 02/10] tools/libxc: introduce setup() and cleanup() on save
Next by Date: Re: [Xen-devel] [PATCH Remus v2 04/10] tools/libxc: introduce DECLARE_HYPERCALL_BUFFER_USER_POINTER
Previous by thread: Re: [Xen-devel] [PATCH Remus v2 01/10] tools/libxc: adjust the memory allocation for migration
Next by thread: Re: [Xen-devel] [PATCH Remus v2 01/10] tools/libxc: adjust the memory allocation for migration
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.