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

[Xen-devel] [PATCH 04/11] [XEN] NUMA memory allocation strategies


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Dulloor <dulloor@xxxxxxxxx>
  • Date: Sun, 4 Apr 2010 15:30:22 -0400
  • Delivery-date: Sun, 04 Apr 2010 12:36:54 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=T1sQid4Ajd8JlkKAqs/lqqLQFy1vQ2spbU/v0F4FOXctVbBFDND0nKrW3o+2X9ph+L de3LK3g5UXNSP0dZ/zCWdC7ARL6u/zDYA9Kou5mm/HUOjGxFRkZvzj6ZgAEnKqiyFsLh lzcvR/u6AzvUPrd/FgESwaSFzlTx81daVegKQ=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

The patch implements the CONFINE/STRIPE/SPLIT NUMA allocation strategies :

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

-dulloor

Signed-off-by: Dulloor Rao <dulloor@xxxxxxxxxx>

Attachment: xen-04-node-mem-allocation.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

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