From: Dario Faggioli <raistlin@linux.it>
To: Zhigang Wang <zhigang.x.wang@oracle.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Ian Campbell <Ian.Campbell@citrix.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 16:00:57 +0200 [thread overview]
Message-ID: <1338472857.9414.10.camel@Abyss> (raw)
In-Reply-To: <4FC76ED8.1040800@oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 1308 bytes --]
On Thu, 2012-05-31 at 09:15 -0400, Zhigang Wang wrote:
> > 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?
>
I looked a bit into this and found out there has been some discussion
already on why such a "counter" (sockets_per_node) has been removed and
shouldn't be reintroduced, and those archs yielding fractional numbers
for it seem to be right that cause:
http://old-list-archives.xen.org/xen-changelog/2010-04/msg00074.html
http://old-list-archives.xen.org/archives/html/xen-devel/2010-02/msg00005.html
Not sure what TheRightThing is here, just wanted to point these out...
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-05-31 14:00 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
2012-05-31 14:00 ` Dario Faggioli [this message]
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=1338472857.9414.10.camel@Abyss \
--to=raistlin@linux.it \
--cc=Ian.Campbell@citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xen.org \
--cc=zhigang.x.wang@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.