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

[Xen-devel] RE: Host Numa informtion in dom0

To: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>, "Kamble, Nitin A" <nitin.a.kamble@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] RE: Host Numa informtion in dom0
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Date: Thu, 11 Feb 2010 15:21:41 +0000
Accept-language: en-US
Acceptlanguage: en-US
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Delivery-date: Thu, 11 Feb 2010 07:22:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <54B2EB610B7F1340BB6A0D4CA04A4F1012BABB2E@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <8EA2C2C4116BF44AB370468FBF85A7770123904A29@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4FA716B1526C7C4DB0375C6DADBC4EA342D83D9EBC@xxxxxxxxxxxxxxxxxxxxxxxxx> <54B2EB610B7F1340BB6A0D4CA04A4F1012BABB2E@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqhN4DFeKntxDxZTHGQrdKilppA4QAi60twAgS0dYAAVccrwA==
Thread-topic: Host Numa informtion in dom0
> > If guest NUMA is disabled, we just use a single node mask which is the
> > union of the per-VCPU node masks.
> >
> > Where allowed node masks span more than one physical node, we should
> > allocate memory to the guest's virtual node by pseudo randomly striping
> > memory allocations (in 2MB chunks) from across the specified physical
> > nodes. [pseudo random is probably better than round robin]
> 
> Do we really want to support this? I don't think the allowed node masks
> should span more than one physical NUMA node. We also need to look at I/O
> devices as well.

Given that we definitely need this striping code in the case where the guest is 
non NUMA, I'd be inclined to still allow it to be used even if the guest has 
multiple NUMA nodes. It could come in handy where there is a hierarchy between 
physical NUMA nodes, enabling for example striping to be used between a pair of 
'close' nodes, while exposing the higher-level topology of sets of the paired 
nodes to be exposed to the guest. 

Ian



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

<Prev in Thread] Current Thread [Next in Thread>