From: Karel Zak <kzak@redhat.com>
To: Dave Hansen <dave@sr71.net>
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 13:45:29 +0200 [thread overview]
Message-ID: <20140919114529.GD5366@x2.net.home> (raw)
In-Reply-To: <20140918193334.C065EBCE@viggo.jf.intel.com>
On Thu, Sep 18, 2014 at 12:33:34PM -0700, Dave Hansen wrote:
> The sysfs effects here cause an issue with the hwloc tool where
> it gets confused and thinks there are more sockets than are
> physically present.
>
> Before this patch, there are two packages:
>
> # cd /sys/devices/system/cpu/
> # cat cpu*/topology/physical_package_id | sort | uniq -c
> 18 0
> 18 1
>
> But 4 _sets_ of core siblings:
>
> # cat cpu*/topology/core_siblings_list | sort | uniq -c
> 9 0-8
> 9 18-26
> 9 27-35
> 9 9-17
>
> After this set, there are only 2 sets of core siblings, which
> is what we expect for a 2-socket system.
>
> # cat cpu*/topology/physical_package_id | sort | uniq -c
> 18 0
> 18 1
> # cat cpu*/topology/core_siblings_list | sort | uniq -c
> 18 0-17
> 18 18-35
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/).
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-09-19 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 19:33 [PATCH] x86: new topology for multi-NUMA-node CPUs Dave Hansen
2014-09-18 20:49 ` Peter Zijlstra
2014-09-18 21:57 ` Dave Hansen
2014-09-19 11:45 ` Karel Zak [this message]
2014-09-19 18:15 ` Dave Hansen
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=20140919114529.GD5366@x2.net.home \
--to=kzak@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=bp@alien8.de \
--cc=brice.goglin@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@sr71.net \
--cc=hpa@linux.intel.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 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.