From: beth kon <eak@us.ibm.com>
To: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@unisys.com>
Cc: Xen-devel@lists.xensource.com
Subject: Re: [PATCH] nr_cpus calculation problem due to incorrectsockets_per_node
Date: Fri, 19 Oct 2007 14:27:09 -0400 [thread overview]
Message-ID: <4718F6FD.2030103@us.ibm.com> (raw)
In-Reply-To: <4C02909CDA7BF14384D8A3F2FA01E89807A25B69@USEA-EXCH2.na.uis.unisys.com>
This patch does not address how many CPUs are recognized by Xen, it just
addresses the number of CPUs reported via xm info. Without this patch,
on asymmetric NUMA machines, xm info would report an incorrect nr_cpus
and sockets_per_node.
The patch does not address building with max_phys_cpus=128, but I have
only been able to build and boot with max_phys_cpus=64. With 128 the
build breaks, so apparently other changes are required, but I haven't
investigated what.
Puthiyaparambil, Aravindh wrote:
>Beth,
>
>With this patch you are able to come up with 128 logical CPUs on x86_64
>Xen? I.E you did a compile with max_phys_cpus=128 and successfully
>booted? Don't you need to also increase NR_RESERVED_GDT_PAGES based on
>number of CPUs among other things?
>
>Thanks,
>
>Aravindh Puthiyaparambil
>Virtualization Engineer
>Virtual Systems Development
>Unisys, Tredyffrin PA
>
>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com
>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of beth kon
>Sent: Friday, October 19, 2007 10:47 AM
>To: Xen-devel@lists.xensource.com; xen-ppc-devel@lists.xensource.com;
>xen-ia64-devel@lists.xensource.com
>Subject: [Xen-devel] [PATCH] nr_cpus calculation problem due to
>incorrectsockets_per_node
>
>Testing on an 8-node 128-way NUMA machine has exposed a problem with
>Xen's nr_cpus calculation. In this case, since Xen cuts off recognized
>CPUs at 32, the machine appears to have 16 CPUs on the first and second
>nodes and none on the remaining nodes. Given this asymmetry, the
>calculation of sockets_per_node (which is later used to calculate
>nr_cpus) is incorrect:
>
>pi->sockets_per_node = num_online_cpus() /(num_online_nodes() *
>pi->cores_per_socket * pi->threads_per_core);
>
>The most straightforward solution is to remove sockets_per_node, and
>instead determine nr_cpus directly from num_online_cpus.
>
>This patch has been tested on x86_64 NUMA machines.
>
>
>
--
Elizabeth Kon (Beth)
IBM Linux Technology Center
Open Hypervisor Team
email: eak@us.ibm.com
next prev parent reply other threads:[~2007-10-19 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 14:47 [PATCH] nr_cpus calculation problem due to incorrect sockets_per_node beth kon
2007-10-19 17:22 ` [PATCH] nr_cpus calculation problem due to incorrectsockets_per_node Puthiyaparambil, Aravindh
2007-10-19 18:27 ` beth kon [this message]
2007-10-29 15:37 ` [PATCH] nr_cpus calculation problem due to incorrect sockets_per_node beth kon
2007-10-29 15:46 ` Keir Fraser
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=4718F6FD.2030103@us.ibm.com \
--to=eak@us.ibm.com \
--cc=Xen-devel@lists.xensource.com \
--cc=aravindh.puthiyaparambil@unisys.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.