linux/sched/sd_flags.h

13  * SHARED_CHILD: These flags are meant to be set from the base domain upwards.
14  * If a domain has this flag set, all of its children should have it set. This
16  * domain share the same resource), or because they are tied to a scheduling
20  * In those cases it doesn't make sense to have the flag set for a domain but
26  * SHARED_PARENT: These flags are meant to be set from the highest domain
27  * downwards. If a domain has this flag set, all of its parents should have it
29  * certain level (e.g. domain starts spanning CPUs outside of the base CPU's
38  * NEEDS_GROUPS: These flags are only relevant if the domain they are set on has
48  * SHARED_CHILD: Set from the base domain up to cpuset.sched_relax_domain_level.
56  * SHARED_CHILD: Set from the base domain up to the NUMA reclaim level.
64  * SHARED_CHILD: Set from the base domain up to the NUMA reclaim level.
72  * SHARED_CHILD: Set from the base domain up to cpuset.sched_relax_domain_level.
80  * SHARED_CHILD: Set from the base domain up to the NUMA reclaim level.
85  * Domain members have different CPU capacities
87  * SHARED_PARENT: Set from the topmost domain down to the first domain where
94  * Domain members share CPU capacity (i.e. SMT)
96  * SHARED_CHILD: Set from the base domain up until spanned CPUs no longer share
103  * Domain members share CPU package resources (i.e. caches)
105  * SHARED_CHILD: Set from the base domain up until spanned CPUs no longer share
116  *                domain has this flag set, then all of its parents need to have
118  * NEEDS_GROUPS: No point in preserving domain if it has a single group.
123  * Place busy tasks earlier in the domain
126  *               up, but currently assumed to be set from the base domain
133  * Prefer to place tasks in a sibling domain
154  * NEEDS_GROUPS: No point in preserving domain if it has a single group.