Hello,
s/inherite/inherit/ in the subject.
On Wed, Aug 21, 2013 at 05:59:44PM +0800, Li Zefan wrote:
> We're going to have separate user-configured masks and effective ones.
>
> At last configured masks can only be changed by writing cpuset.cpus
> and cpuset.mems, and they won't be restricted by parent cpuset. While
> effective masks reflect cpu/memory hotplug and hierachical restriction.
>
> This is a preparation to make real_{cpus,mems}_allowed to be effective
> masks of the cpuset:
>
> - change the effective masks at hotplug: done
> - change the effective masks at config change: done
> - take on ancestor's mask when the effective mask is empty: done
The above description doesn't really work well. It looks like this
patch does all three changes. Can you please update the patch
descriptions so that it's clear what each patch does?
> /*
> + * If it becomes empty, inherite the effective mask of the
^
inherit
> + * parent, which is guarantted to have some CPUs.
> */
> - if (cpumask_equal(new_cpus, cp->real_cpus_allowed) &&
> - ((cp == cs) || !cpumask_empty(new_cpus))) {
> + if (cpumask_empty(new_cpus))
> + cpumask_copy(new_cpus, parent->real_cpus_allowed);
> +
> + /* Skip the whole subtree if the cpumask is not changed. */
> + if (cpumask_equal(new_cpus, cp->real_cpus_allowed)) {
> pos_css = css_rightmost_descendant(pos_css);
> continue;
> }
Ooh, I like how this looks now. Makes a lot more sense than the logic
before.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
