From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andre Przywara <andre.przywara@amd.com>
Subject: Re: NUMA TODO-list for xen-devel
Date: Fri, 3 Aug 2012 13:26:06 +0200
Message-ID: <501BB54E.1050302@amd.com>
References: <1343837796.4958.32.camel@Solace> <501BA1C0.7040100@amd.com>
	<501BC6B8020000780009277B@nat28.tlf.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <501BC6B8020000780009277B@nat28.tlf.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: Anil Madhavapeddy <anil@recoil.org>, Andrew Cooper <Andrew.Cooper3@citrix.com>, xen-devel <xen-devel@lists.xen.org>, Dario Faggioli <raistlin@linux.it>, George Dunlap <dunlapg@gmail.com>, Yang Z Zhang <yang.z.zhang@intel.com>
List-Id: xen-devel@lists.xenproject.org

On 08/03/2012 12:40 PM, Jan Beulich wrote:
>>>> On 03.08.12 at 12:02, Andre Przywara <andre.przywara@amd.com> wrote:
>> On 08/01/2012 06:16 PM, Dario Faggioli wrote:
>>> Hi everyone,
>>>
>>> With automatic placement finally landing into xen-unstable, I stated
>>> thinking about what I could work on next, still in the field of
>>> improving Xen's NUMA support. Well, it turned out that running out of
>>> things to do is not an option! :-O
>>>
>>> In fact, I can think of quite a bit of open issues in that area, that I'm
>>> just braindumping here.
>>
>>> ...
>>>
>>>          * automatic placement of Dom0, if possible (my current series is
>>>            only affecting DomU)
>>
>> I think Dom0 NUMA awareness should be one of the top priorities. If I
>> boot my 8-node box with Xen, I end up with a NUMA-clueless Dom0 which
>> actually has memory from all 8 nodes and thinks it's memory is flat.
>> There are some tricks to confine it to node 0 (dom0_mem=<memory of
>> node0> dom0_vcpus=<cores in node0> dom0_vcpus_pin), but this requires
>> intimate knowledge of the systems parameters and is error-prone.
>
> How about "dom0_mem=node<n> dom0_vcpus=node<n>" as
> an extension to the current options?

Yes, that sounds like a good idea. And relatively easy to implement.
Maybe a list or a number of nodes (to make it more complicated ;-)

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany