Le 08/09/2016 17:59, Dave Love a écrit :
> Brice Goglin writes:
>
>> Hello
>> It's not a feature. This should work fine.
>> Random guess: do you have NUMA headers on your build machine ? (package
>> libnuma-dev or numactl-devel)
>> (hwloc-info --support also report whether membinding is support
On Thu, Sep 8, 2016 at 8:59 AM, Dave Love wrote:
> Brice Goglin writes:
>
> > Hello
> > It's not a feature. This should work fine.
> > Random guess: do you have NUMA headers on your build machine ? (package
> > libnuma-dev or numactl-devel)
> > (hwloc-info --support also report whether membindin
Brice Goglin writes:
> Hello
> It's not a feature. This should work fine.
> Random guess: do you have NUMA headers on your build machine ? (package
> libnuma-dev or numactl-devel)
> (hwloc-info --support also report whether membinding is supported or not)
> Brice
Oops, you're right! Thanks. I
Hello
It's not a feature. This should work fine.
Random guess: do you have NUMA headers on your build machine ? (package
libnuma-dev or numactl-devel)
(hwloc-info --support also report whether membinding is supported or not)
Brice
Le 08/09/2016 16:34, Dave Love a écrit :
> I'm somewhat confused
I'm somewhat confused by binding on Knights Landing -- which is probably
a feature.
I'm looking at a KNL box configured as "Cluster Mode: SNC4 Memory Mode:
Cache" with hwloc 1.11.4; I've read the KNL hwloc FAQ entries. I ran
openmpi and it reported failure to bind memory (but binding to cores was
