[RFC,1/3] sched/core: Introduce SD_ASYM_CPUCAPACITY_FULL sched_domain flag
diff mbox series

Message ID 1618578085-29584-2-git-send-email-beata.michalska@arm.com
State New
Headers show
  • Rework CPU capacity asymmetry detection
Related show

Commit Message

Beata Michalska April 16, 2021, 1:01 p.m. UTC
Introducing new, complementary to SD_ASYM_CPUCAPACITY, sched_domain
topology flag, to distinguish between shed_domains where any CPU
capacity asymmetry is detected (SD_ASYM_CPUCAPACITY) and ones where
a full range of CPU capacities is visible to all domain members

With the distinction between full and partial CPU capacity asymmetry,
the scope of the original SD_ASYM_CPUCAPACITY flag gets shifted, still
maintaining the existing behaviour when one is detected on a given
sched domain, allowing misfit migrations within sched domains that
do not observe full range of CPU capacities but still do have members
with different capacity values. It loses though it's meaning when it
comes to the lowest CPU asymmetry sched_domain level per-cpu pointer,
which is to be now denoted by SD_ASYM_CPUCAPACITY_FULL flag.

Signed-off-by: Beata Michalska <beata.michalska@arm.com>
 include/linux/sched/sd_flags.h | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff mbox series

diff --git a/include/linux/sched/sd_flags.h b/include/linux/sched/sd_flags.h
index 34b21e9..57bde66 100644
--- a/include/linux/sched/sd_flags.h
+++ b/include/linux/sched/sd_flags.h
+ * Domain members have different CPU capacities spanning all unique CPU
+ * capacity values.
+ *
+ * SHARED_PARENT: Set from the topmost domain down to the first domain where
+ *		  all available CPU capacities are visible
+ * NEEDS_GROUPS: Per-CPU capacity is asymmetric between groups.
+ */
  * Domain members share CPU capacity (i.e. SMT)
  * SHARED_CHILD: Set from the base domain up until spanned CPUs no longer share