Yes. Most of locality info comes from /sys/... on Linux.
Brice
Le 29/09/2014 22:59, Vishwanath Venkatesan a écrit :
> Thanks for the quick response, yes lstopo -l does make the numbers
> contiguous.
> Another question I had was, how does hwloc populate the information
> that certain cpus share a
Thanks for the quick response, yes lstopo -l does make the numbers
contiguous.
Another question I had was, how does hwloc populate the information that
certain cpus share a particular cache?
is it form sys/.../cache/index*/shared_cpu_list?
Thanks
Vish
On Mon, Sep 29, 2014 at 1:47 PM, Samuel
Vishwanath Venkatesan, le Mon 29 Sep 2014 13:38:35 -0700, a écrit :
> I was trying to use HWLOC on Ivybridge. I found that there is some
> inconsistency in the core numbering.
>
> In the attached image (generated from running lstopo (hwloc - 1.9.1), we can
> see that cores 6,7 do not exist
Hi,
I was trying to use HWLOC on Ivybridge. I found that there is some
inconsistency in the core numbering.
In the attached image (generated from running lstopo (hwloc - 1.9.1), we
can see that cores 6,7 do not exist although, PU#6 and PU#7 does exist.
Could you have a look and let me know?
Le 29/09/2014 19:01, Aulwes, Rob a écrit :
> Hi,
>
> I'm trying to allocate and bind memory on the same NUMA domain as the
> calling thread. The code I use is as follows.
>
> /* retrieve the single PU where the current thread actually
> runs within this process binding */
>
>
>
Hi,
I'm trying to allocate and bind memory on the same NUMA domain as the calling
thread. The code I use is as follows.
/* retrieve the single PU where the current thread actually runs within
this process binding */
int err = hwloc_get_last_cpu_location(topo, set,