Sorry guys, I think I have all patches ready since the F2F meeting, but
I couldn't test them enough because ranking was broken. I'll work on
that by next week.

Brie



Le 22/05/2018 à 17:50, r...@open-mpi.org a écrit :
> I’ve been running with hwloc 2.0.1 for quite some time now without problem, 
> including use of the shared memory segment. It would be interesting to hear 
> what changes you had to make.
>
> However, that said, there is a significant issue in ORTE when trying to 
> map-by NUMA as hwloc 2.0.1 no longer associates cpus with NUMA regions. So 
> you’ll get an error when you try it. Unfortunately, that is the default 
> mapping policy when #procs > 2.
>
>
>> On May 22, 2018, at 8:46 AM, Vallee, Geoffroy R. <valle...@ornl.gov> wrote:
>>
>> Hi,
>>
>> HWLOC 2.0.x support was brought up during the call. FYI, I am currently 
>> using (and still testing) hwloc 2.0.1 as an external library with master and 
>> I did not face any major problem; I only had to fix minor things, mainly for 
>> putting the HWLOC topology in a shared memory segment. Let me know if you 
>> want me to help with the effort of supporting HWLOC 2.0.x.
>>
>> Thanks,
>> _______________________________________________
>> devel mailing list
>> devel@lists.open-mpi.org
>> https://lists.open-mpi.org/mailman/listinfo/devel
> _______________________________________________
> devel mailing list
> devel@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/devel

_______________________________________________
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel

Reply via email to