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:32:51

Samuel Thibault wrote:
> Brice Goglin, le Fri 29 Jan 2010 22:48:13 +0100, a écrit :
>> I am looking at the remaining tickets for v1.0. Assuming there are no
>> "critical" warning anymore, and assuming we have done enough for people
>> to combine network topologies (manually for now), only 2 ticket remains:
>> #12 support user-defined processor restriction
>> #21 Allow lookup of specific PIDs
>> I understand #12 but I am not sure what #21 actually needs. We would do
>> a get_cpubind(pid) and then what ? Do a processor restriction as defined
>> in #12 ?
> There is a difference between the current CPU binding (#12) and
> detecting the topology as if being called from another process (and
> getting a different view of the machine because of different applied
> cpusets, etc.)

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.