Re: [PATCH] cpuset code prevents binding tasks to new cpus
From: Paul Jackson
Date: Mon Aug 21 2006 - 19:03:23 EST
> - top_cpuset.cpus_allowed = cpu_online_map;
> + top_cpuset.cpus_allowed = cpu_possible_map;
While this seems sensible on systems not using cpusets (but still using
kernels configured for cpusets), it is surprising on systems using
cpusets, on which one expects the cpuset that a task is in to reflect
the cpus that a task is allowed to use.
A long time ago, this code actually had cpu_possible_map here, not
cpu_online_map. That was changed, in the patch:
[Patch] cpusets interoperate with hotplug online maps
Lets discuss this further. See further my previous reply to Anton.
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@xxxxxxx> 1.925.600.0401
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/