RE: [PATCH 00/11] PV NUMA Guests

[Ian Pratt <Ian.Pratt@eu.citrix.com>]

> The set of patches implements virtual NUMA-enlightenment to support
> NUMA-aware PV guests. In more detail, the patch implements the
> following :
> 
> * For the NUMA systems, the following memory allocation strategies are
> implemented :
>  - CONFINE : Confine the VM memory allocation to a single node. As
> opposed to the current method of doing this in python, the patch
> implements this in libxc(along with other strategies) and with
> assurance that the memory actually comes from the selected node.

Do you use the VCPU affinity masks to determine the node in question, or is there another parameter to specify this?

Thanks,
Ian


> - STRIPE : If the VM memory doesn't fit in a single node and if the VM
> is not compiled with guest-numa-support, the memory is allocated
> striped across a selected max-set of nodes.
> - SPLIT : If the VM memory doesn't fit in a single node and if the VM
> is compiled with guest-numa-support, the memory is allocated split
> (equally for now) from the min-set of nodes. The  VM is then made
> aware of this NUMA allocation (virtual NUMA enlightenment).
> -DEFAULT : This is the existing allocation scheme.
> 
> * If the numa-guest support is compiled into the PV guest, we add
> numa-guest-support to xen features elfnote. The xen tools use this to
> determine if SPLIT strategy can be applied.
> 
> * The PV guest uses the virtual NUMA enlightenment to setup its NUMA
> layout (at the time of initmem_init)
> 
> Please comment.
> 
> -dulloor
> 
> Signed-off-by: Dulloor Rao <dulloor@gatech.edu>
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel