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] Xen-devel [XEN PATCH] [Linux-PVOPS] ballooning on numa

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen-devel [XEN PATCH] [Linux-PVOPS] ballooning on numa domains
From: Dulloor <dulloor@xxxxxxxxx>
Date: Mon, 9 Nov 2009 09:18:37 -0500
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Mon, 09 Nov 2009 06:19:01 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=o3ImJiJYtlkH+Z+QPItm+YUrzWAiyz4+hAs+4nKparI=; b=Y/pzgFxjmuQv2YNvmVT68E4S4K4EA/iHZ1fGQpYgN8cKToFPUO9kCB2hCyxil7Op0R tndP/a4F7sw5OPSFGIRB3fNBDH0RGnuy0VFWwVZrTdT/XqLO7HGbxrQE+zcxET6WwUBb mCRQy78f153qly3eZ2gsyeDuefjyWOiofSfHA=
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=Td8ANPFgCLwQ5U6wQuX4xE4qjHKjIf+yHfhVYHiNbO6OEFVPk32HAA4/SKaJab3l51 TqRJkmzDyVaIPIhjPegJCq2LCYlWH12qefZqz0DVTzJRMMK/+uNM2IPLGwSVmeazsKIL 4vVWXK9gbXFATJhyBRYISoy2Gf2IdDRyhuf+I=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AF81FCB020000780001E7AB@xxxxxxxxxxxxxxxxxx>
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: <940bcfd20911082340x25ebdccep3984b4acc2d6ac57@xxxxxxxxxxxxxx> <4AF7E8EC020000780001E68E@xxxxxxxxxxxxxxxxxx> <940bcfd20911090235y704d163el4347a805e5a90b4f@xxxxxxxxxxxxxx> <4AF81FCB020000780001E7AB@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Nov 9, 2009 at 7:57 AM, Jan Beulich <JBeulich@xxxxxxxxxx> wrote:
>>>> Dulloor <dulloor@xxxxxxxxx> 09.11.09 11:35 >>>
>>-  dom0 can read the numa tables (same as xen). Also, the memory map
>>for dom0 is (currently) set in a way that the numa ranges are
>>consistent. I don't see that changing, so I feel the assumption is
> Pseudo-consistent at best - there's no reason to believe that the node
> a physical page appears to live on (by looking up its address in the SRAT)
> has any relationship to the node it really lives on.
> And even if that was the case, you could easily end up with many (up to
> all but one) nodes appearing unpopulated (due to dom0_mem=).

Agreed pseudo-consistent (offseted by alloc_spfn). But, even with the
dom0_mem set,
the numa ranges are silently clipped, so the mappings are still

>>- XENMEMF flags are indeed meant for xen tools. But, ballooning is
>>completely xen specific too ... it is a xen tool, except that it
>>resides in domain's kernel/tree.
> That doesn't help you with the node ID issue: The tools can make
> meaningful use of Xen node IDs; if you want to do this in the kernel
> you'll have to establish a kernel<->Xen translation of node IDs.
For other guest domains, we will need translation (part of my next patches).
But, for dom0, translation is implicit due to shared acpi tables.

I could work on a patch to make mappings fully consistent (by rigging the
slit/srat values as seen by dom0), inertia being an interface acceptable to
Linux folks. Do we need that ?

> Jan

Xen-devel mailing list