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

RE: [Xen-devel] [PATCH] xm info

To: <david.nospam.hopwood@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] xm info
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Sun, 3 Jul 2005 23:32:26 +0100
Delivery-date: Sun, 03 Jul 2005 22:31:18 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWAHPtXttYwHUQjRwKL+kV8FqdY0QAAfBIA
Thread-topic: [Xen-devel] [PATCH] xm info
 > Ian Pratt wrote:
> > While we're at it, I'd suggest we add an extra level of hierarchy , 
> > 'nodes', for NUMA, even if we have nodes hardwired to 1 at 
> present e.g.:
> > 
> >>logical_cpus           : 1
> >>nodes                  : 1
> >>sockets_per_node       : 1
> >>cores_per_socket       : 1
> >>hyperthreads_per_core  : 1
> 
> Is sockets_per_node always the same for each node (similarly 
> for cores_per_socket and hyperthreads_per_core)?

In systems where this wan't the case we'd just have the 'missing cores'
permanently marked down.

Ian

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