I just pushed my patches rebased on master + update to hwloc 2.0.1 to
bgoglin/ompi (master branch).

My testing of mapping/ranking/binding looks good here (on dual xeon with
CoD, 2 sockets x 2 NUMA x 6 cores).

It'd be nice if somebody else could test on another platform with
different options and/or advanced options (PPR, PE, etc).

Brice




Le 23/05/2018 à 17:07, Vallee, Geoffroy R. a écrit :
> I totally missed that PR before I sent my email, sorry. It pretty much covers 
> all the modifications I made. :) Let me know if I can help in any way.
>
> Thanks,
>
>> On May 22, 2018, at 11:49 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> 
>> wrote:
>>
>> Geoffroy -- check out https://github.com/open-mpi/ompi/pull/4677.
>>
>> If all those issues are now moot, great.  I really haven't followed up much 
>> since I made the initial PR; I'm happy to have someone else take it over...
>>
>>
>>> On May 22, 2018, at 11: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
>>
>> -- 
>> Jeff Squyres
>> jsquy...@cisco.com
>>
>> _______________________________________________
>> 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