From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Cc: Ricardo Neri <ricardo.neri@intel.com>,
"Ravi V. Shankar" <ravi.v.shankar@intel.com>,
Ben Segall <bsegall@google.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Len Brown <len.brown@intel.com>, Mel Gorman <mgorman@suse.de>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
Tim Chen <tim.c.chen@linux.intel.com>,
Valentin Schneider <vschneid@redhat.com>,
Ionela Voinescu <ionela.voinescu@arm.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
"Tim C . Chen" <tim.c.chen@intel.com>
Subject: Re: [PATCH v3 04/10] sched/fair: Let low-priority cores help high-priority busy SMT cores
Date: Mon, 13 Feb 2023 14:40:24 +0100 [thread overview]
Message-ID: <3a41995b-c39c-7346-e04b-7f13433b51c2@arm.com> (raw)
In-Reply-To: <20230207045838.11243-5-ricardo.neri-calderon@linux.intel.com>
On 07/02/2023 05:58, Ricardo Neri wrote:
[...]
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 80c86462c6f6..c9d0ddfd11f2 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -10436,11 +10436,20 @@ static struct rq *find_busiest_queue(struct lb_env *env,
> nr_running == 1)
> continue;
>
> - /* Make sure we only pull tasks from a CPU of lower priority */
> + /*
> + * Make sure we only pull tasks from a CPU of lower priority
> + * when balancing between SMT siblings.
> + *
> + * If balancing between cores, let lower priority CPUs help
> + * SMT cores with more than one busy sibling.
> + */
> if ((env->sd->flags & SD_ASYM_PACKING) &&
> sched_asym_prefer(i, env->dst_cpu) &&
> - nr_running == 1)
> - continue;
> + nr_running == 1) {
> + if (env->sd->flags & SD_SHARE_CPUCAPACITY ||
> + (!(env->sd->flags & SD_SHARE_CPUCAPACITY) && is_core_idle(i)))
> + continue;
is_core_idle(i) returns true for !CONFIG_SCHED_SMP. So far it was always
guarded by `flags & SD_SHARE_CPUCAPACITY` which is only set for
CONFIG_SCHED_SMP.
Here it's different but still depends on `flags & SD_ASYM_PACKING`.
Can we have SD_ASYM_PACKING w/o CONFIG_SCHED_SMP? The comment just says
`If balancing between cores (MC), let lower priority CPUs help SMT cores
with more than one busy sibling.`
So this only mentions your specific asymmetric e-cores w/o SMT and
p-cores w/ SMT case.
I'm asking since numa_idle_core(), the only user of is_core_idle() so
far has an extra `!static_branch_likely(&sched_smt_present)` condition
before calling it.
> + }
>
> switch (env->migration_type) {
> case migrate_load:
> @@ -10530,8 +10539,20 @@ asym_active_balance(struct lb_env *env)
> * lower priority CPUs in order to pack all tasks in the
> * highest priority CPUs.
> */
> - return env->idle != CPU_NOT_IDLE && (env->sd->flags & SD_ASYM_PACKING) &&
> - sched_asym_prefer(env->dst_cpu, env->src_cpu);
> + if (env->idle != CPU_NOT_IDLE && (env->sd->flags & SD_ASYM_PACKING)) {
> + /* Always obey priorities between SMT siblings. */
> + if (env->sd->flags & SD_SHARE_CPUCAPACITY)
> + return sched_asym_prefer(env->dst_cpu, env->src_cpu);
> +
> + /*
> + * A lower priority CPU can help an SMT core with more than one
> + * busy sibling.
> + */
> + return sched_asym_prefer(env->dst_cpu, env->src_cpu) ||
> + !is_core_idle(env->src_cpu);
Here it is similar.
> + }
> +
> + return false;
next prev parent reply other threads:[~2023-02-13 13:40 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 4:58 [PATCH v3 00/10] sched/fair: Avoid unnecessary migrations within SMT domains Ricardo Neri
2023-02-07 4:58 ` [PATCH v3 01/10] sched/fair: Generalize asym_packing logic for SMT cores Ricardo Neri
2023-02-07 4:58 ` [PATCH v3 02/10] sched/fair: Move is_core_idle() out of CONFIG_NUMA Ricardo Neri
2023-02-07 4:58 ` [PATCH v3 03/10] sched/fair: Only do asym_packing load balancing from fully idle SMT cores Ricardo Neri
2023-02-07 4:58 ` [PATCH v3 04/10] sched/fair: Let low-priority cores help high-priority busy " Ricardo Neri
2023-02-08 7:56 ` Vincent Guittot
2023-02-09 11:53 ` Peter Zijlstra
2023-02-10 0:43 ` Ricardo Neri
2023-02-10 8:41 ` Peter Zijlstra
2023-02-10 13:05 ` Ricardo Neri
2023-02-10 1:52 ` Ricardo Neri
2023-02-13 13:40 ` Dietmar Eggemann [this message]
2023-02-13 23:23 ` Ricardo Neri
2023-03-10 0:51 ` Tim Chen
2023-03-14 23:54 ` Ricardo Neri
2023-02-07 4:58 ` [PATCH v3 05/10] sched/fair: Keep a fully_busy SMT sched group as busiest Ricardo Neri
2023-02-07 4:58 ` [PATCH v3 06/10] sched/fair: Use the prefer_sibling flag of the current sched domain Ricardo Neri
2023-02-08 7:48 ` Vincent Guittot
2023-02-10 13:24 ` Ricardo Neri
2023-02-09 13:17 ` Chen Yu
2023-02-09 20:00 ` Chen, Tim C
2023-02-09 23:05 ` Tim Chen
2023-02-10 3:16 ` Ricardo Neri
2023-02-10 6:55 ` Chen Yu
2023-02-10 10:08 ` Peter Zijlstra
2023-02-10 14:54 ` Valentin Schneider
2023-02-10 16:53 ` Peter Zijlstra
2023-02-10 17:12 ` Valentin Schneider
2023-02-10 18:31 ` Ricardo Neri
2023-02-13 12:17 ` Dietmar Eggemann
2023-02-14 6:43 ` Ricardo Neri
2023-02-16 5:21 ` Ricardo Neri
2023-02-16 12:16 ` Peter Zijlstra
2023-02-17 1:41 ` Ricardo Neri
2023-02-23 10:09 ` Dietmar Eggemann
2023-02-24 12:29 ` Ricardo Neri
[not found] ` <tencent_60A804570F09C0CFE0495D5B984941123A05@qq.com>
2023-02-20 9:45 ` Valentin Schneider
[not found] ` <tencent_6C38D389245FD03C6E1312999FEDD394F606@qq.com>
2023-02-21 18:15 ` Valentin Schneider
2023-02-07 4:58 ` [PATCH v3 07/10] sched/fair: Do not even the number of busy CPUs via asym_packing Ricardo Neri
2023-02-13 12:44 ` Dietmar Eggemann
2023-02-13 19:47 ` Ricardo Neri
2023-02-07 4:58 ` [PATCH v3 08/10] sched/topology: Remove SHARED_CHILD from ASYM_PACKING Ricardo Neri
2023-03-03 11:29 ` Ionela Voinescu
2023-03-05 19:08 ` Ricardo Neri
2023-03-06 13:10 ` Ionela Voinescu
2023-03-06 18:17 ` Ricardo Neri
2023-02-07 4:58 ` [PATCH v3 09/10] x86/sched: Remove SD_ASYM_PACKING from the SMT domain flags Ricardo Neri
2023-02-07 4:58 ` [PATCH v3 10/10] x86/sched/itmt: Give all SMT siblings of a core the same priority Ricardo Neri
2023-02-09 8:07 ` [PATCH v3 00/10] sched/fair: Avoid unnecessary migrations within SMT domains Zhang, Rui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3a41995b-c39c-7346-e04b-7f13433b51c2@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=ionela.voinescu@arm.com \
--cc=juri.lelli@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=ricardo.neri@intel.com \
--cc=rostedt@goodmis.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tim.c.chen@intel.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome