On 12/1/21 13:05, Waiman Long wrote:
On 12/1/21 11:46, Tejun Heo wrote:
So, when we were first adding the partition support, the thinking was
that
as it's pretty niche anyway, we can take some aberrations and
restrictions,
but I don't think it's a good direction to be building up on top of
those
like this and would much prefer to clean up the rules and
restrictions. I
know that this has been going on for quite a while and am sorry that am
coming back to the same issue repeatedly which isn't necessarily
caused by
the proposed change. What do you think?
I think I can relax some of the restrictions, but probably not all of
them at this time. We can certainly working on removing as much
restriction and limitations as possible in future update to the
partition code.
I would say that partition is a cpuset feature that only a minority of
users may ever need to use. What I don't want to do is to make the
partition feature as general and accommodating as possible and then some
of them become dead code that people never use. It won't break binary
compatibility to relax or remove limitations in the future. However,
imposing new limitation or restriction in the future may not be
possible. So I would like to see new use cases evolve that require us to
remove the limitations. If that happens, I am happy to update the code
to accommodate the new use cases.
For the current use cases of partition that I am aware of, the current
limitations as documented will not be a problem for those use cases.
The document below is my latest draft of the document. There are several
major changes from the earlier draft:
1) The limitation that "cpuset.cpus" has to be a superset of child's
"cpuset.cpus" has been removed as a new patch to remove that limitation
will be added.
2) The initial transition from "member" to partition root now requires
that "cpuset.cpus" overlap with that of the parent's "cpuset.cpus"
instead of being a superset.
3) Now read back of "cpuset.cpus.partition" may return "isolated invalid".
For the transition back to "member", I haven't changed the current
wording of forcing child partition roots to become "member" yet. If you
think keeping them as invalid partition root is better, I can made that
change too.
Please let me know what other changes you would like to see.
Cheers,
Longman
----------------------------------------------------------------------------------------
cpuset.cpus.partition
A read-write single value file which exists on non-root
cpuset-enabled cgroups. This flag is owned by the parent cgroup
and is not delegatable.
It accepts only the following input values when written to.
======== ================================
"member" Non-root member of a partition
"root" Partition root
"isolated" Partition root without load balancing
======== ================================
The root cgroup is always a partition root and its state
cannot be changed. All other non-root cgroups start out as
"member".
When set to "root", the current cgroup is the root of a new
partition or scheduling domain that comprises itself and
all its descendants except those that are separate partition
roots themselves and their descendants.
The value shown in "cpuset.cpus.effective" of a partition root is
the CPUs that the parent partition root can dedicate to the new
partition root. They are subtracted from "cpuset.cpus.effective"
of the parent and may be different from "cpuset.cpus"
When set to "isolated", the CPUs in that partition root will
be in an isolated state without any load balancing from the
scheduler. Tasks placed in such a partition with multiple
CPUs should be carefully distributed and bound to each of the
individual CPUs for optimal performance.
A partition root ("root" or "isolated") can be in one of the
two possible states - valid or invalid. An invalid partition
root is in a degraded state where some state information are
retained, but behaves more like a "member".
On read, the "cpuset.cpus.partition" file can show the following
values.
====================== ==============================
"member" Non-root member of a partition
"root" Partition root
"isolated" Partition root without load balancing
"root invalid (<reason>)" Invalid partition root
"isolated invalid (<reason>)" Invalid isolated partition root
====================== ==============================
In the case of an invalid partition root, a descriptive string on
why the partition is invalid is included within parentheses.
Almost all possible state transitions among "member", valid
and invalid partition roots are allowed except from "member"
to invalid partition root.
Before the "member" to partition root transition can happen,
the following conditions must be met or the transition will
not be allowed.
1) The "cpuset.cpus" is non-empty and exclusive, i.e. they are
not shared by any of its siblings.
2) The parent cgroup is a valid partition root.
3) The "cpuset.cpus" must contain at least one of the CPUs from
parent's "cpuset.cpus", i.e. they overlap.
4) There is no child cgroups with cpuset enabled. This avoids
cpu migrations of multiple cgroups simultaneously which can
be problematic.
Once becoming a partition root, the only rule restricting
changes made to "cpuset.cpus" is the exclusivity rule where
none of the siblings of a partition root can share CPUs with
it.
External events like hotplug or inappropriate changes to
"cpuset.cpus" can cause a valid partition root to become invalid.
Besides the exclusivity rule listed above, the other conditions
required to maintain the validity of a partition root are
as follows:
1) The parent cgroup is a valid partition root.
2) If "cpuset.cpus.effective" is empty, the partition must have
no task associated with it. Otherwise, the partition becomes
invalid and "cpuset.cpus.effective" will fall back to that
of the nearest non-empty ancestor.
A corollary of a valid partition root is that
"cpuset.cpus.effective" is always a subset of "cpuset.cpus".
Note that a task cannot be moved to a cgroup with empty
"cpuset.cpus.effective".
Changing a partition root (valid or invalid) to "member" is
always allowed. If there are child partition roots underneath
it, however, they will be forced to be switched back to "member"
too and lose their partitions. So care must be taken to double
check for this condition before disabling a partition root.
A valid non-root parent partition may distribute out all its CPUs
to its child partitions when there is no task associated with it.
An invalid partition root can be reverted back to a valid one
if none of the validity constraints of a valid partition root
are violated.
Poll and inotify events are triggered whenever the state of
"cpuset.cpus.partition" changes. That includes changes caused by
write to "cpuset.cpus.partition", cpu hotplug and other changes
that make the partition invalid. This will allow user space
agents to monitor unexpected changes to "cpuset.cpus.partition"
without the need to do continuous polling.
