Re: [Xen-devel] [RFC][PATCH 2/2] Add hcall to probe Xen heap

[Ryan Harper <ryanh@xxxxxxxxxx>]

* Subrahmanian, Raj <raj.subrahmanian@xxxxxxxxxx> [2007-06-19 17:32]:
> Ryan
> >> I was able to see the node info from xm info
> >> node_to_cpu            : node0:24-31
> >>                          node1:16-23
> >>                          node2:8-15
> >>                          node3:0-7
> >
> >Yeah, in xm info, I'd like to see:
> >
> >nr_cpus
> >nr_nodes
> >sockets_per_node
> >cores_per_socket
> >threads_per_core
> >
> nr_cpus                : 32
> nr_nodes               : 4
> sockets_per_node       : 8
> cores_per_socket       : 1
> threads_per_core       : 1
> cpu_mhz                : 3400
> hw_caps                :
> bfebfbff:20100800:00000000:00000180:0000e5bd:00000000:0
> 0000001
> total_memory           : 130943
> free_memory            : 128740
> node_to_cpu            : node0:24-31
>                          node1:16-23
>                          node2:8-15
>                          node3:0-7
> 
> The cores per socket and sockets per node are off.
> These are dual-core, 4 socket nodes.

Hrm, ok.  I think if the cores_per_socket were fixed, then the
sockets_per_node calc would fix itself.  I've not touched the
cores_per_socket calculation; that will need some attention, but I
assume that value has always been incorrect, ie, not a NUMA issue.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@xxxxxxxxxx

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