Samuel Thibault, le Sat 30 Jan 2010 15:55:00 +0100, a écrit :
> #21 implicitly does: "what cpuset they're bound to" is just an example.
> A configuration function hwloc_topology_set_pid(topology, pid) would
> mean that the discovery has to be done from the view of the given pid,
> and thus the allowed_cpuset should be according to that view, thus
> administrative restrictions.
Just to give an example: lstopo --pid 1234 would not only show where the
process is currently bound to, but also its allowed cpuset, which can be
useful when monitoring applications run by a batch scheduler or such.