From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [vNUMA v2][PATCH 2/8] public interface Date: Wed, 4 Aug 2010 06:27:37 +0100 Message-ID: References: <4C589051.2020806@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C589051.2020806@amd.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: Andre Przywara , Dulloor Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 03/08/2010 22:55, "Andre Przywara" wrote: >> As such, the purpose of vnode-to-mnode translation is for the enlightened >> guests to know where their underlying memory comes from, so that >> over-provisioning features >> like ballooning are given a chance to maintain this distribution. > I was afraid you were saying that ;-) I haven't thought about this in > detail, but maybe we can make an exception for Dom0 only, because this > is the most prominent and frequent user of ballooning. But I really > think that DomUs should not know about or deal with host NUMA nodes. So long as it gets renamed to 'node_id' in the info structure I'm okay with it. That doesn't preclude simply setting that field to 0...nr_vnodes-1 and doing translation in the hypervisor, but also leaves us a bit of flexibility. -- Keir