On 2/9/2012 1:19 PM, Brice Goglin wrote:
> So you can find out that you are "bound" by a Linux cgroup (I am not
> saying Linux "cpuset" to avoid confusion) by comparing root->cpuset and
> root->online_cpuset.
If I understood the problem as stated earlier in this thread the current
code was looping over a (singleton) cpuset and not finding finding the
current process to be bound to any of the cpus in the set. For that
case the fact that the cpuset is a singleton should already have been
enough information to know that one is effectively bound. Is there
really more to this than a need for special-casing the singleton?
-Paul
--
Paul H. Hargrove PHHargrove_at_[hidden]
Future Technologies Group
HPC Research Department Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
|
![[Flag]](../../../../../community/mirrors/flag-us.gif){kind=small}