From: Ian Campbell Subject: Re: [PATCH RFC v2 4/7] libxl/vNUMA: vNUMA libxl functionality. Date: Tue, 17 Sep 2013 17:38:39 +0100 Message-ID: <1379435919.11304.187.camel@hastur.hellion.org.uk> References: <1379062216-13855-1-git-send-email-ufimtseva@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: Li Yechen , Dario Faggioli , Stefano Stabellini , Ian Jackson , "xen-devel@lists.xen.org" , Elena Ufimtseva , sw@linux.com List-Id: xen-devel@lists.xenproject.org On Tue, 2013-09-17 at 17:36 +0100, George Dunlap wrote: > On Fri, Sep 13, 2013 at 9:50 AM, Elena Ufimtseva wrote: > > vNUMA libxl supporting functionality. > > libxl supporting functionality for vNUMA includes: > > * having vNUMA memory areas sizes, transforms it to > > start and end pfns based on domain e820 map; > > * contructs vnode_to_pnode map for vNUMA nodes memory > > allocation and pass it to Xen; the mechanism considers > > automatic NUMA placement in case of presence of hardware > > NUMA; In best case scenario all vnodes will be allocated > > within one pnode. If the domain spans different pnodes, > > the vnodes will be one-by-one placed to pnodes. If such > > allocation is impossible due to the memory constraints, > > the allocation will use default mechanism; this is worst > > case scenario. > > Why would someone want to make a VM with two vnodes and then put them > on the same pnode? Apart from testing, of course, but our defaults > should be for the common case of real users. If your pool of machines included 1- and 2-node systems might you want to do this so that when you migrate the vm to a two node system it can make use of it? Ian.