WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [xen-devel][vNUMA v2][PATCH 2/8] public interface

To: Andre Przywara <andre.przywara@xxxxxxx>, Dulloor <dulloor@xxxxxxxxx>
Subject: Re: [xen-devel][vNUMA v2][PATCH 2/8] public interface
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 4 Aug 2010 06:27:37 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 03 Aug 2010 22:29:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C589051.2020806@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcszVrI6N5DBL4mgSRehV+5AhSXmmAAPw2Cd
Thread-topic: [xen-devel][vNUMA v2][PATCH 2/8] public interface
User-agent: Microsoft-Entourage/12.24.0.100205
On 03/08/2010 22:55, "Andre Przywara" <andre.przywara@xxxxxxx> 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



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel