From: Keir Fraser Subject: Re: Xen 3.4.1 NUMA support Date: Tue, 10 Nov 2009 08:57:49 +0000 Message-ID: References: <4AF937A0020000780001EC26@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4AF937A0020000780001EC26@vpn.id2.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , Ian Pratt Cc: George Dunlap , Andre Przywara , Dan Magenheimer , "xen-devel@lists.xensource.com" , Papagiannis Anastasios List-Id: xen-devel@lists.xenproject.org On 10/11/2009 08:51, "Jan Beulich" wrote: >> What default confinement? I thought guests had an all-pCPUs affinity mask be >> default? > > Not with numa=on (see also Andre's post to this effect): The guest will > get assigned to a node, and its affinity set to that node's CPUs. ...And if it didn't, striping would not happen. In fact iirc the default NUMA allocation policy for an all-pcpus domain is in some respects pessimal: vcpu0's initial node gets drained of memory first. I.e., you get *less* 'striping' than you could with numa=off where you might at least get lucky. -- Keir