<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<div class="moz-cite-prefix">Le 04/04/2020 à 21:58, Baptiste Jonglez
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:20200404195832.GG1800446@lud.localdomain">
<pre class="moz-quote-pre" wrap="">On 04-04-20, Brice Goglin wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Using NUMA nodes for CPU sockets is indeed unreliable these days. Most
vendors can expose multiple NUMA nodes per CPU package.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Ok, thanks. Does this also apply to x86?</pre>
</blockquote>
<p><br>
</p>
<p>Yes, I was actually mostly referring about x86 here. Both Intel
Xeon and AMD Epyc can be configured with 2 or 4 NUMA nodes per
package.</p>
<p>That's also true for POWER, some Sparc from Fujitsu, and likely
some ARM processors too (mostly likely the upcoming A64fx from
Fujitsu too).<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:20200404195832.GG1800446@lud.localdomain">
<pre class="moz-quote-pre" wrap="">Also, do you know if it's possible to obtain all information (number of
nodes, packages, cores, pu) in a single call to hwloc-*, ideally with an
easily-parsable output?
</pre>
</blockquote>
<p><br>
</p>
<p>Maybe parse the output of "lstopo -s" (summary of the topology).
Add "--filter all:none --filter package:all --filter core:all" so
that you only get what you want (PU/Machine/NUMA are always
enabled).<br>
</p>
<pre>$ lstopo -s --filter all:none --filter package:all --filter core:all
depth 0: 1 Machine (type #0)
depth 1: 2 Package (type #1)
depth 2: 40 Core (type #2)
depth 3: 80 PU (type #3)
Special depth -3: 4 NUMANode (type #13)
</pre>
<p>Brice</p>
<p><br>
</p>
</body>
</html>