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/
Home Products Support Community News


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

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [xen-devel][vNUMA v2][PATCH 2/8] public interface
From: Dulloor <dulloor@xxxxxxxxx>
Date: Tue, 3 Aug 2010 22:48:58 -0700
Cc: Andre Przywara <andre.przywara@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 03 Aug 2010 22:49:52 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=LL1QYap/ggnmwom948qBAEVWr1iZcd4TxFqVPnROtDk=; b=aVTcoGsQ98bqV6KjbrtWv5CUP4fHlGgUKqkNLTTa3hIqPz0xOXL3ZY+zexlD1I2GGK 6jHmnuXEEeT0Q8OfkmAPpi/ncN4o6RqzwNj4wzBQdF159EMdVv8SBuduHmu/K2/20r/7 ydhlBpWOYKZhmUPzsZJzolucEsjPu4HcVrpo0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=w9SExwAYcY/o6a4Rr6HwYWmbbF6lReghJBy/1wZXOtcFvbIgCVCIF+Ccu4yxD6BIEk WyY7P2N7ibrbX05YQ/E0bPsyKNZkF2Q6pHsmaOJORXwCGM8oILRdp3y8nyONfTvqbxQ9 5smTAPnfDO9YwuQmFgG1s7prv42epq1roV8ck=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C87EB8D9.42B7%keir.fraser@xxxxxxxxxxxxx>
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>
References: <4C589051.2020806@xxxxxxx> <C87EB8D9.42B7%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Aug 3, 2010 at 10:27 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> 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.
Yes, I like this idea. Will do that.

>  -- Keir

Xen-devel mailing list