From: Keir Fraser Subject: Re: Xen 3.4.1 NUMA support Date: Thu, 12 Nov 2009 16:09:55 +0000 Message-ID: References: <4AF84100020000780001E8CC@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4AF84100020000780001E8CC@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 , Andre Przywara , Dan Magenheimer Cc: George Dunlap , "xen-devel@lists.xensource.com" , Papagiannis Anastasios List-Id: xen-devel@lists.xenproject.org On 09/11/2009 15:19, "Jan Beulich" wrote: >>>> Andre Przywara 09.11.09 16:02 >>> >> BTW: Shouldn't we set finally numa=on as the default value? > > I'd say no, at least until the default confinement of a guest to a single > node gets fixed to properly deal with guests having more vCPU-s than > a node's worth of pCPU-s (i.e. I take it for granted that the benefits of > not overcommitting CPUs outweigh the drawbacks of cross-node memory > accesses at the very least for CPU-bound workloads). If this would be fixed (e.g., turn off node locality entirely by default for domains which will not fit into a single node) then I think we could consider numa=on by default. -- Keir