From: Dave Hansen <dave@sr71.net>
To: Karel Zak <kzak@redhat.com>
Cc: linux-kernel@vger.kernel.org, dave.hansen@linux.intel.com,
a.p.zijlstra@chello.nl, mingo@kernel.org, hpa@linux.intel.com,
brice.goglin@gmail.com, bp@alien8.de
Subject: Re: [PATCH] x86: new topology for multi-NUMA-node CPUs
Date: Fri, 19 Sep 2014 11:15:05 -0700 [thread overview]
Message-ID: <541C72A9.9090509@sr71.net> (raw)
In-Reply-To: <20140919114529.GD5366@x2.net.home>
On 09/19/2014 04:45 AM, Karel Zak wrote:
> hmm... it would be also nice to test it with lscpu(1) from
> util-linux (but it uses maps rather than lists from cpu*/topology/).
Here's the output with and with out Cluster-on-Die enabled.
Everything looks OK to me. The cache size changes are what the CPU
actually tells us through CPUID leaves.
[root@otc-grantley-03 ~]# diff -ru lscpu.nocod lscpu.wcod
--- lscpu.nocod 2014-09-19 04:01:17.846336595 -0700
+++ lscpu.wcod 2014-09-19 04:10:56.557383761 -0700
@@ -6,18 +6,20 @@
Thread(s) per core: 2
Core(s) per socket: 18
Socket(s): 2
-NUMA node(s): 2
+NUMA node(s): 4
Vendor ID: GenuineIntel
CPU family: 6
Model: 63
Model name: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
Stepping: 2
-CPU MHz: 1340.468
-BogoMIPS: 4590.53
+CPU MHz: 1360.234
+BogoMIPS: 4590.67
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
-L3 cache: 46080K
-NUMA node0 CPU(s): 0-17,36-53
-NUMA node1 CPU(s): 18-35,54-71
+L3 cache: 23040K
+NUMA node0 CPU(s): 0-8,36-44
+NUMA node1 CPU(s): 9-17,45-53
+NUMA node2 CPU(s): 18-26,54-62
+NUMA node3 CPU(s): 27-35,63-71
next prev parent reply other threads:[~2014-09-19 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 19:33 Dave Hansen
2014-09-18 20:49 ` Peter Zijlstra
2014-09-18 21:57 ` Dave Hansen
2014-09-19 11:45 ` Karel Zak
2014-09-19 18:15 ` Dave Hansen [this message]
2014-09-22 7:43 ` Karel Zak
2014-09-21 17:56 ` Brice Goglin
2014-09-24 14:58 ` [tip:sched/core] x86, sched: Add " tip-bot for Dave Hansen
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=541C72A9.9090509@sr71.net \
--to=dave@sr71.net \
--cc=a.p.zijlstra@chello.nl \
--cc=bp@alien8.de \
--cc=brice.goglin@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@linux.intel.com \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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
Powered by JetHome