From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aron Griffis Subject: Re: [RFC] Xen NUMA strategy Date: Wed, 19 Sep 2007 23:09:38 -0400 Message-ID: <20070920030937.GI28555@fc.hp.com> References: <51CFAB8CB6883745AE7B93B3E084EBE2011113AE@pdsmsx412.ccr.corp.intel.com> <8A87A9A84C201449A0C56B728ACF491E260723@liverpoolst.ad.cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <8A87A9A84C201449A0C56B728ACF491E260723@liverpoolst.ad.cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: Andre Przywara , "Xu, Anthony" , Akio Takebe , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Ian Pratt wrote: [Tue Sep 18 2007, 04:43:24AM EDT] > The way I see it, in most situations it will not make sense for guests > to span NUMA nodes: you'll have a number of guests with relatively small > numbers of vCPUs, and it probably makes sense to allow the guests to be > pinned to nodes. What we have in Xen today works pretty well for this > case, [snip] One part that doesn't work well presently is memory locality. A guest can be pinned to a CPU but its allocated memory might be on a distant node... Aron