From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zhigang Wang Subject: Re: strange cpu number from xm info Date: Thu, 31 May 2012 09:15:04 -0400 Message-ID: <4FC76ED8.1040800@oracle.com> References: <4F7EE57D.4020207@oracle.com> <4F7F57A502000078000821B6@nat28.tlf.novell.com> <4F7F4B82.6040007@oracle.com> <1333784346.12209.108.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1333784346.12209.108.camel@dagon.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Dan Magenheimer , Jan Beulich , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 04/07/2012 03:39 AM, Ian Campbell wrote: > On Fri, 2012-04-06 at 21:01 +0100, Zhigang Wang wrote: >> On 04/06/2012 03:52 PM, Jan Beulich wrote: >>>>>> Zhigang Wang 04/06/12 2:45 PM >>> >>>> nr_cpus : 8 >>>> nr_nodes : 1 >>>> cores_per_socket : 4 >>>> threads_per_core : 1 >>>> >>>> I thought nr_cpus = nr_nodes * cores_per_socket * threads_per_core >>> nr_cpus = nr_nodes * sockets_per_node * cores_per_socket * threads_per_core >> It seems on xm/xl info we don't show how many sockets_per_node. Can we do that >> in the future? > We can and should. Are you able to send a patch for xl at least? > > Here is another case: # xm info ... nr_cpus : 48 nr_nodes : 8 cores_per_socket : 12 threads_per_core : 1 This HP BL685 G7 (4 socket x 12 cores). Actually sockets_per_node = 0.5. Xen calculates it correctly. Should we should s 0.5 for sockets_per_node? Or just ignore sockets_per_node? Thanks, Zhigang