Hardware Locality Development Mailing List Archives

Subject: Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction
From: Samuel Thibault (samuel.thibault_at_[hidden])
Date: 2010-02-15 17:22:56

• Next message: MPI Team: "[hwloc-devel] Create success (hwloc r1.0a1r1728)"
• Previous message: Ashley Pittman: "Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction"
• In reply to: Ashley Pittman: "Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction"

Ashley Pittman, le Mon 15 Feb 2010 22:16:16 +0000, a écrit :
> I suspect the right thing to do is to from my perspective is to report the affinity rather than the cpuset then or rather whichever of the two is most restrictive which will be the affinity if it's set and the cpuset if it's not.

Then I'd say you just need a --pid option in hwloc-bind, to get the
current binding, which will be restricted by the administrative rules
already.

Samuel

• Next message: MPI Team: "[hwloc-devel] Create success (hwloc r1.0a1r1728)"
• Previous message: Ashley Pittman: "Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction"
• In reply to: Ashley Pittman: "Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction"