On 10/12/21 10:39 AM, Michal Koutný wrote:
On Wed, Oct 06, 2021 at 02:21:03PM -0400, Waiman Long <llong@xxxxxxxxxx> wrote:
Sorry for not following up with this patchset sooner as I was busy on other
tasks.
Thanks for continuing with this.
1) The "cpuset.cpus" is not empty and the list of CPUs are
exclusive, i.e. they are not shared by any of its siblings.
2) The parent cgroup is a partition root.
3) The "cpuset.cpus" is a subset of the union of parent's
"cpuset.cpus.effective" and offlined CPUs in parent's
"cpuset.cpus".
4) There is no child cgroups with cpuset enabled. This avoids
cpu migrations of multiple cgroups simultaneously which can
be problematic.
A partition, when enabled, can be in an invalid state. An example
Thanks for the comments.
is when its parent is also an invalid partition.
You say:
"it can only be enabled in a cgroup if all the following conditions are met.",
"2) The parent cgroup is a partition root."
and then the example:
"A partition, when enabled, can be in an invalid state. An example is
when its parent is also an invalid partition."
But the first two statements imply you can't have enabled the partition
in such a case.
Yes, you are right. We should not allow enabling partition when the
parent is an invalid right. I will fix that.
I think there is still mixup of partition validity conditions and
transition conditions, yours would roughly divide into (not precisely,
just to share my understanding):
Validity conditions
1) The "cpuset.cpus" is not empty and the list of CPUs are
exclusive, i.e. they are not shared by any of its siblings.
2) The parent cgroup is a partition root.
Transition conditions:
3) The "cpuset.cpus" is a subset of the union of parent's
"cpuset.cpus.effective" and offlined CPUs in parent's
"cpuset.cpus".
I am going to change this condition to just "cpuset.cpus" is a subset of
parent's "cpuset.cpus". After some deliberation, I had concluded it
doesn't make sense from the system partition planning point of view to
allow a valid partition to contain cpus that are not in the designated
"cpuset.cpus". That will automatically included offlined cpus in
parent's "cpuset.cpus".
4) There is no child cgroups with cpuset enabled. This avoids
cpu migrations of multiple cgroups simultaneously which can
be problematic.
(I've put no. 3 into transition conditions because _after_ the
transition parent's cpuset.cpus.effective are subtracted the new root's
cpuset.cpus but I'd like to have something similar as a validity
condition but I haven't come up with that yet.)
I consider the following situation:
r // all cpus 0-7
`- part1 cpus=0-3 root >partition
` subpart1 cpus=0-1 root >partition
` subpart2 cpus=2-3 root >partition
`- other cpus=4-7 // member by default
Both subpart1 and subpart2 are valid partition roots.
Look at actions listed below (as alternatives, not a sequence):
a) hotplug offlines cpu 3
- would part1 still be considered a valid root?
- perhaps not
- would subpart1 still be considered a valid root?
- it could be, but its parent is invalid so no?
- would subpart2 still be considered a valid root?
- perhaps not
They will all be valid roots. They will become invalid only when their
effective cpus are empty and there are tasks in the partition.
b) administrative change writes 0-2 into part1 cpus
That is actually not allowed because of the following code in
validate_change():
static int validate_change(struct cpuset *cur, struct cpuset *trial)
{
:
/* Each of our child cpusets must be a subset of us */
ret = -EBUSY;
cpuset_for_each_child(c, css, cur)
if (!is_cpuset_subset(c, trial))
goto out;
- would part1 still be considered a valid root?
- yes
- would subpart1 still be considered a valid root?
- yes
- would subpart2 still be considered a valid root?
- perhaps not
c) administrative change writes 3-7 into `other` cpus
- should this fail or invalidate a root partition part1?
- perhaps fail since the same "owner" manages all siblings and
should reduce part1 first
Again, this will not be allowed because of the CPU_EXCLUSIVE flag set in
part1.
The answers above are just my "natural" responses, the ideal may be
different. The issue I want to illustrate is that if all the conditions
are formed as transition conditions only, they can't be used to reason
about hotplug or config changes (except for cpuset.cpus.partitions
writes).
What would help me with the understanding -- the invalid root partition is defined as
1) such a cgroup where no cpus are granted from the top (and thus has to fall back to ancestors)
or
2) such a cgroup where cpus requested in cpuset.cpus can't be fulfilled (i.e. any missing invalidates)?
For a valid partition, "cpuset.cpus.effective" is always a subset of
"cpuset.cpus". When "cpuset.cpus.effective" becomes empty and there are
tasks in the partition, it becomes invalid and inherent the non-empty
cpuset.cpus.effective of the nearest ancestor. The condition that causes
"cpuset.cpus.effective" to become empty can be hotplug or changes to
"cpuset.cpus".
Furthermore, another example (motivated by the patch 4/6)
r // all cpus 0-7
`- part1 cpus=0-4 root >partition
` subpart1 cpus=0-1 root >partition
` subpart2 cpus=2-3 root >partition
` task
`- other cpus=5-7 // member by default
It's a valid and achievable state (even on v2 since cpuset is a threaded
controller).
a) cpu 4 is offlined
- this should invalidate part1 (and propagate invalidation into
subpart1 and subpart2).
That is subject to design. My current thought is to keep part1 as valid
but invalidate the child partitions (subpart1 and subpart2).
b) administrative write 0-3 into part1 cpus
- should this invalidate part1 or be rejected?
The result should be the same as (a).
In conclusion, it'd be good to have validity conditions separate from
transition conditions (since hotplug transition can't be rejected) and
perhaps treat administrative changes from an ancestor equally as a
hotplug.
I am trying to make the result of changing "cpuset.cpus" as close to
hotplug as possible but there are cases where the "cpuset.cpus" change
is prohibited but hotplug can still happen to remove the cpu.
Hope this will help to clarify the current design.
Cheers,
Longman
