From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: strange cpu number from xm info
Date: Fri, 06 Apr 2012 16:01:06 -0400 [thread overview]
Message-ID: <4F7F4B82.6040007@oracle.com> (raw)
In-Reply-To: <4F7F57A502000078000821B6@nat28.tlf.novell.com>
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?
It seems this machine has: sockets_per_node = 2.
Thanks very much Jan.
Zhigang
next prev parent reply other threads:[~2012-04-06 20:01 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 [this message]
2012-04-06 21:09 ` Dan Magenheimer
2012-04-07 7:39 ` Ian Campbell
2012-05-31 13:15 ` Zhigang Wang
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=4F7F4B82.6040007@oracle.com \
--to=zhigang.x.wang@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).