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

Dulloor wrote:
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
Yes, I like this idea. Will do that.
Ack, that sounds good. So we have virtual nodes, virtual physical nodes and machine nodes.


Andre Przywara
AMD-OSRC (Dresden)
Tel: x29712

Xen-devel mailing list