Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Hardware Locality Development mailing list

Subject: Re: [hwloc-devel] processor restriction + lookup of pid for 1.0
From: Brice Goglin (Brice.Goglin_at_[hidden])
Date: 2010-01-30 09:47:26


Samuel Thibault wrote:
> Brice Goglin, le Sat 30 Jan 2010 15:32:51 +0100, a écrit :
>
>> I still don't see much difference. In #12, you get_cpubind(pid=0) and
>> use the resulting cpuset to restrict our topology. In #21, you
>> get_cpubind(another pid) and apply the cpuset to restrict our topology
>> as well.
>>
>
> No: the administrative restriction cpuset is not the same as the current
> cpuset binding of the target process.
>

Neither #12 nor #21 talks about adminstrative restriction...

So we'd need this ?
1) hwloc_topology_from_cpu/membind(pid) (or cpuset as argument) =>
restrict topology to given cpu/membind
2) hwloc_topology_get_from_pid(pid) reads both cpu/membind and
administrative restrictions from another process instead of current process

Brice