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

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] cpuset code prevents binding tasks to new cpus
  - From: Paul Jackson <[email protected]>

References:
- cpusets not cpu hotplug aware
  - From: Anton Blanchard <[email protected]>
- Re: cpusets not cpu hotplug aware
  - From: Paul Jackson <[email protected]>
- Re: cpusets not cpu hotplug aware
  - From: Anton Blanchard <[email protected]>
- [PATCH] cpuset code prevents binding tasks to new cpus
  - From: Nathan Lynch <[email protected]>
- Re: [PATCH] cpuset code prevents binding tasks to new cpus
  - From: Paul Jackson <[email protected]>

Prev by Date: [PATCH] ks0127: wire up i2c_add_driver() return value
Next by Date: Re: [PATCH] [LIBATA] [mm] change path to libata in libata.tmpl
Previous by thread: Re: [PATCH] cpuset code prevents binding tasks to new cpus
Next by thread: Re: [PATCH] cpuset code prevents binding tasks to new cpus
Index(es):
- Date
- Thread

[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]