Re: [PATCH] cpuset code prevents binding tasks to new cpus

[Nathan Lynch]

Paul Jackson wrote:
> Nathan wrote:
> > -	top_cpuset.cpus_allowed = cpu_online_map;
> > +	top_cpuset.cpus_allowed = cpu_possible_map;
> 
> NAQ
> 
> 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.

Will it actually break anything?

-
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/