@@ -2190,75 +2190,93 @@ Cpuset Interface Files
2190
2190
2191
2191
It accepts only the following input values when written to.
2192
2192
2193
- ======== ================================
2194
- "root" a partition root
2195
- "member" a non-root member of a partition
2196
- ======== ================================
2197
-
2198
- When set to be a partition root, the current cgroup is the
2199
- root of a new partition or scheduling domain that comprises
2200
- itself and all its descendants except those that are separate
2201
- partition roots themselves and their descendants. The root
2202
- cgroup is always a partition root.
2203
-
2204
- There are constraints on where a partition root can be set.
2205
- It can only be set in a cgroup if all the following conditions
2206
- are true.
2207
-
2208
- 1) The "cpuset.cpus" is not empty and the list of CPUs are
2209
- exclusive, i.e. they are not shared by any of its siblings.
2210
- 2) The parent cgroup is a partition root.
2211
- 3) The "cpuset.cpus" is also a proper subset of the parent's
2212
- "cpuset.cpus.effective".
2213
- 4) There is no child cgroups with cpuset enabled. This is for
2214
- eliminating corner cases that have to be handled if such a
2215
- condition is allowed.
2216
-
2217
- Setting it to partition root will take the CPUs away from the
2218
- effective CPUs of the parent cgroup. Once it is set, this
2219
- file cannot be reverted back to "member" if there are any child
2220
- cgroups with cpuset enabled.
2221
-
2222
- A parent partition cannot distribute all its CPUs to its
2223
- child partitions. There must be at least one cpu left in the
2224
- parent partition.
2225
-
2226
- Once becoming a partition root, changes to "cpuset.cpus" is
2227
- generally allowed as long as the first condition above is true,
2228
- the change will not take away all the CPUs from the parent
2229
- partition and the new "cpuset.cpus" value is a superset of its
2230
- children's "cpuset.cpus" values.
2231
-
2232
- Sometimes, external factors like changes to ancestors'
2233
- "cpuset.cpus" or cpu hotplug can cause the state of the partition
2234
- root to change. On read, the "cpuset.sched.partition" file
2235
- can show the following values.
2236
-
2237
- ============== ==============================
2238
- "member" Non-root member of a partition
2239
- "root" Partition root
2240
- "root invalid" Invalid partition root
2241
- ============== ==============================
2242
-
2243
- It is a partition root if the first 2 partition root conditions
2244
- above are true and at least one CPU from "cpuset.cpus" is
2245
- granted by the parent cgroup.
2246
-
2247
- A partition root can become invalid if none of CPUs requested
2248
- in "cpuset.cpus" can be granted by the parent cgroup or the
2249
- parent cgroup is no longer a partition root itself. In this
2250
- case, it is not a real partition even though the restriction
2251
- of the first partition root condition above will still apply.
2252
- The cpu affinity of all the tasks in the cgroup will then be
2253
- associated with CPUs in the nearest ancestor partition.
2254
-
2255
- An invalid partition root can be transitioned back to a
2256
- real partition root if at least one of the requested CPUs
2257
- can now be granted by its parent. In this case, the cpu
2258
- affinity of all the tasks in the formerly invalid partition
2259
- will be associated to the CPUs of the newly formed partition.
2260
- Changing the partition state of an invalid partition root to
2261
- "member" is always allowed even if child cpusets are present.
2193
+ ========== =====================================
2194
+ "member" Non-root member of a partition
2195
+ "root" Partition root
2196
+ "isolated" Partition root without load balancing
2197
+ ========== =====================================
2198
+
2199
+ The root cgroup is always a partition root and its state
2200
+ cannot be changed. All other non-root cgroups start out as
2201
+ "member".
2202
+
2203
+ When set to "root", the current cgroup is the root of a new
2204
+ partition or scheduling domain that comprises itself and all
2205
+ its descendants except those that are separate partition roots
2206
+ themselves and their descendants.
2207
+
2208
+ When set to "isolated", the CPUs in that partition root will
2209
+ be in an isolated state without any load balancing from the
2210
+ scheduler. Tasks placed in such a partition with multiple
2211
+ CPUs should be carefully distributed and bound to each of the
2212
+ individual CPUs for optimal performance.
2213
+
2214
+ The value shown in "cpuset.cpus.effective" of a partition root
2215
+ is the CPUs that the partition root can dedicate to a potential
2216
+ new child partition root. The new child subtracts available
2217
+ CPUs from its parent "cpuset.cpus.effective".
2218
+
2219
+ A partition root ("root" or "isolated") can be in one of the
2220
+ two possible states - valid or invalid. An invalid partition
2221
+ root is in a degraded state where some state information may
2222
+ be retained, but behaves more like a "member".
2223
+
2224
+ All possible state transitions among "member", "root" and
2225
+ "isolated" are allowed.
2226
+
2227
+ On read, the "cpuset.cpus.partition" file can show the following
2228
+ values.
2229
+
2230
+ ============================= =====================================
2231
+ "member" Non-root member of a partition
2232
+ "root" Partition root
2233
+ "isolated" Partition root without load balancing
2234
+ "root invalid (<reason>)" Invalid partition root
2235
+ "isolated invalid (<reason>)" Invalid isolated partition root
2236
+ ============================= =====================================
2237
+
2238
+ In the case of an invalid partition root, a descriptive string on
2239
+ why the partition is invalid is included within parentheses.
2240
+
2241
+ For a partition root to become valid, the following conditions
2242
+ must be met.
2243
+
2244
+ 1) The "cpuset.cpus" is exclusive with its siblings , i.e. they
2245
+ are not shared by any of its siblings (exclusivity rule).
2246
+ 2) The parent cgroup is a valid partition root.
2247
+ 3) The "cpuset.cpus" is not empty and must contain at least
2248
+ one of the CPUs from parent's "cpuset.cpus", i.e. they overlap.
2249
+ 4) The "cpuset.cpus.effective" cannot be empty unless there is
2250
+ no task associated with this partition.
2251
+
2252
+ External events like hotplug or changes to "cpuset.cpus" can
2253
+ cause a valid partition root to become invalid and vice versa.
2254
+ Note that a task cannot be moved to a cgroup with empty
2255
+ "cpuset.cpus.effective".
2256
+
2257
+ For a valid partition root with the sibling cpu exclusivity
2258
+ rule enabled, changes made to "cpuset.cpus" that violate the
2259
+ exclusivity rule will invalidate the partition as well as its
2260
+ sibiling partitions with conflicting cpuset.cpus values. So
2261
+ care must be taking in changing "cpuset.cpus".
2262
+
2263
+ A valid non-root parent partition may distribute out all its CPUs
2264
+ to its child partitions when there is no task associated with it.
2265
+
2266
+ Care must be taken to change a valid partition root to
2267
+ "member" as all its child partitions, if present, will become
2268
+ invalid causing disruption to tasks running in those child
2269
+ partitions. These inactivated partitions could be recovered if
2270
+ their parent is switched back to a partition root with a proper
2271
+ set of "cpuset.cpus".
2272
+
2273
+ Poll and inotify events are triggered whenever the state of
2274
+ "cpuset.cpus.partition" changes. That includes changes caused
2275
+ by write to "cpuset.cpus.partition", cpu hotplug or other
2276
+ changes that modify the validity status of the partition.
2277
+ This will allow user space agents to monitor unexpected changes
2278
+ to "cpuset.cpus.partition" without the need to do continuous
2279
+ polling.
2262
2280
2263
2281
2264
2282
Device controller
0 commit comments