Re: [regression] cpuset,mm: update tasks' mems_allowed in time(58568d2)

[David Rientjes]

On Wed, 24 Feb 2010, Miao Xie wrote:

> I think it is not a big deal because it is safe and doesn't cause any problem.
> Beside that, task->cpus_allowed is initialized to cpu_possible_mask on the no-cpuset
> kernel, so using cpu_possible_mask to initialize task->cpus_allowed is reasonable.
> (top cpuset is a special cpuset, isn't it?)
>  

I'm suprised that I can create a descendant cpuset of top_cpuset that 
cannot include all of its parents' cpus and that the root cpuset's cpus 
mask doesn't change when cpus are onlined/offlined.
--
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/