Lines Matching refs:t
124 to another cgroup. Migration of a process doesn't affect already
146 # mount -t cgroup2 none $MOUNT_POINT
242 zombie process does not appear in "cgroup.procs" and thus can't be
245 A cgroup which doesn't have any children or live processes can be
246 destroyed by removing the directory. Note that a cgroup which doesn't
281 The ones which don't are called domain controllers.
298 can't have populated child cgroups which aren't threaded. Because the
313 Once threaded, the cgroup can't be made a domain again. To enable the
328 C is created as a domain but isn't connected to a parent which can
329 host child domains. C can't be used until it is turned into a
360 aren't tied to a specific thread belong to the threaded domain cgroup.
432 controller interface files - anything which doesn't start with
444 the parent has the controller enabled and a controller can't be
452 only when they don't have any processes of their own. In other words,
453 only domain cgroups which don't contain any processes can have domain
462 processes and anonymous resource consumption which can't be associated
469 Note that the restriction doesn't get in the way if there is no
471 important as otherwise it wouldn't be possible to create children of a
492 shouldn't be allowed to write to them. For the first method, this is
506 Currently, cgroup doesn't impose any restrictions on the number of
515 can't be moved into or out of the sub-hierarchy by the delegatee.
528 processes around freely in the delegated sub-hierarchy it can't pull
584 character for collision avoidance. Also, interface file names won't
588 cgroup doesn't do anything to prevent name collisions and it's the
667 resource. Allocations can't be over-committed - the sum of the
674 As allocations can't be over-committed, some configuration
731 shouldn't have resource control interface files.
815 It can't be populated or have controllers enabled. It may
935 A process can't enter a dying cgroup under any circumstances,
936 a dying cgroup can't revive.
963 Frozen status of a cgroup doesn't affect any cgroup tree operations:
991 and doesn't need pass enablement via ancestors from root.
1025 WARNING: cgroup2 doesn't yet support control of realtime processes and
1169 won't be reclaimed under any conditions. If there is no
1195 memory won't be reclaimed unless there is no reclaimable
1232 this limit and can't be reduced, the OOM killer is invoked in
1239 Some kinds of allocations don't invoke the OOM killer.
1356 can show up in the middle. Don't rely on items remaining in a
1555 can show up in the middle. Don't rely on items remaining in a
1652 Because breach of the high limit doesn't trigger the OOM killer but
1658 memory usage doesn't indicate whether the workload can benefit from
1664 memory; unfortunately, memory pressure monitoring mechanism isn't
1673 to a different cgroup doesn't move the memory usages that it
1811 The IO cost model isn't expected to be accurate in absolute
1924 doesn't update it until the page is released, even if writeback
1926 areas wouldn't work as expected. It's recommended to avoid such usage
1974 target the controller doesn't do anything. Once a group starts missing its
2160 and won't be affected by any CPU hotplug events.
2200 and won't be affected by any memory nodes hotplug events.
2210 a need to change "cpuset.mems" with active tasks, it shouldn't
2512 This section contains information that isn't considered to be a part of
2674 # mount -t cgroup2 none $MOUNT_POINT
2709 While this function doesn't care exactly when it's called
2751 provide a high level of flexibility, it wasn't useful in practice.
2756 the fact that controllers couldn't be moved to another hierarchy once
2759 hierarchy. It wasn't possible to vary the granularity depending on
2776 that a thread's cgroup membership couldn't be described in finite
2783 Also, as a controller couldn't have any expectation regarding the
2790 completely orthogonal to each other isn't necessary. What usually is
2803 This didn't make sense for some controllers and those controllers
2858 wasn't obvious or universal, and there were various other knobs which
2859 simply weren't available for threads.
2865 always added an extra layer of nesting which wouldn't be necessary
2869 The memory controller didn't have a way to control what happened
2890 forked and executed for each event. The event delivery wasn't