xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
	Jan Beulich <jbeulich@suse.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: strange cpu number from xm info
Date: Thu, 31 May 2012 09:15:04 -0400	[thread overview]
Message-ID: <4FC76ED8.1040800@oracle.com> (raw)
In-Reply-To: <1333784346.12209.108.camel@dagon.hellion.org.uk>

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 <zhigang.x.wang@oracle.com> 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

  reply	other threads:[~2012-05-31 13:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 12:45 strange cpu number from xm info Zhigang Wang
2012-04-06 19:52 ` Jan Beulich
2012-04-06 20:01   ` Zhigang Wang
2012-04-06 21:09     ` Dan Magenheimer
2012-04-07  7:39     ` Ian Campbell
2012-05-31 13:15       ` Zhigang Wang [this message]
2012-05-31 14:00         ` Dario Faggioli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FC76ED8.1040800@oracle.com \
    --to=zhigang.x.wang@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=jbeulich@suse.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).