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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

A long time ago, this code actually had cpu_possible_map here, not
cpu_online_map.  That was changed, in the patch:

  http://lkml.org/lkml/2004/9/12/104
  [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 <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux