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: A question about changeset 20621:f9392f6eda79 and Discon

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "andre.przywara@xxxxxxx" <andre.przywara@xxxxxxx>
Subject: [Xen-devel] RE: A question about changeset 20621:f9392f6eda79 and Discontinuous online node
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Wed, 6 Jan 2010 17:39:24 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 06 Jan 2010 01:39:50 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C76A0847.5882%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: <C8EDE645B81E5141A8C6B2F73FD92651138B5973C3@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C76A0847.5882%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqOqEbbnXIv78APQI2JXa+pIXFSLwAAvgW+AADQapAAAQga/wAAXUzQ
Thread-topic: A question about changeset 20621:f9392f6eda79 and Discontinuous online node
Sure.

--jyh

>-----Original Message-----
>From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
>Sent: Wednesday, January 06, 2010 5:29 PM
>To: Jiang, Yunhong; andre.przywara@xxxxxxx
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: A question about changeset 20621:f9392f6eda79 and Discontinuous
>online node
>
>On 06/01/2010 09:07, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:
>
>>> In the case of the node_to_cpu list returned by xc.physinfo(), it already
>>> accounts for holes in node space by having empty lists of cpus for those
>>> non-existent or empty nodes. Should just be a case of having the xend python
>>> code understand that as necessary?
>>
>> Keir, thanks for pointing out this.The API is sufficient. We only need 
>> changes
>> to python side to understand this. One minor thing is, maybe we need change
>> the nr_nodes from number of online node to the maxium of online node id,
>> otherwise, xc.physinfo may have no idea when iterate the node_to_memory
>> information (will it be possible the a node has only memory populated, while
>> no CPU populated?)
>
>Yes, I think actually that would be a bug fix, given how tools currently use
>the nr_nodes field. Feel free to send a patch as part of your fix-up work: I
>don't think even changing the field name is necessary, but we can add a
>comemnt to sysctl.h.
>
> -- Keir
>


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