From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Jeffrey Hugo <jhugo@codeaurora.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Austin Christ <austinwc@codeaurora.org>,
Tyler Baicar <tbaicar@codeaurora.org>
Subject: Re: [RFC 1/2] sched/fair: Fix load_balance() affinity redo path
Date: Mon, 15 May 2017 15:56:20 +0100 [thread overview]
Message-ID: <9b97fa6f-2b3d-3e10-fd55-208ef47f3e2a@arm.com> (raw)
In-Reply-To: <9580a899-0fdb-7c14-c6e5-397f7d52bcf2@codeaurora.org>
On 12/05/17 21:57, Jeffrey Hugo wrote:
> On 5/12/2017 2:47 PM, Peter Zijlstra wrote:
>> On Fri, May 12, 2017 at 11:01:37AM -0600, Jeffrey Hugo wrote:
>>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>>> index d711093..8f783ba 100644
>>> --- a/kernel/sched/fair.c
>>> +++ b/kernel/sched/fair.c
>>> @@ -8219,8 +8219,19 @@ static int load_balance(int this_cpu, struct
>>> rq *this_rq,
>>> /* All tasks on this runqueue were pinned by CPU affinity */
>>> if (unlikely(env.flags & LBF_ALL_PINNED)) {
>>> + struct cpumask tmp;
>>
>> You cannot have cpumask's on stack.
>
> Well, we need a temp variable to store the intermediate values since the
> cpumask_* operations are somewhat limited, and require a "storage"
> parameter.
>
> Do you have any suggestions to meet all of these requirements?
What about we use env.dst_grpmask and check if cpus is an improper
subset of env.dst_grpmask? In this case we have to get rid of
setting env.dst_grpmask = NULL in case of CPU_NEWLY_IDLE which is
IMHO not an issue since it's idle is passed via env into
can_migrate_task().
And cpus has to be and'ed with sched_domain_span(env.sd).
I'm not sure if this will work with 'not fully connected NUMA' (SD_OVERLAP)
though ...
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index a903276fcb62..2ede4c1c9db8 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -6737,10 +6737,10 @@ int can_migrate_task(struct task_struct *p, struct lb_env *env)
* our sched_group. We may want to revisit it if we couldn't
* meet load balance goals by pulling other tasks on src_cpu.
*
- * Also avoid computing new_dst_cpu if we have already computed
- * one in current iteration.
+ * Avoid computing new_dst_cpu for NEWLY_IDLE or if we have
+ * already computed one in current iteration.
*/
- if (!env->dst_grpmask || (env->flags & LBF_DST_PINNED))
+ if (env->idle == CPU_NEWLY_IDLE || (env->flags & LBF_DST_PINNED))
return 0;
/* Prevent to re-select dst_cpu via env's cpus */
@@ -8091,14 +8091,7 @@ static int load_balance(int this_cpu, struct rq *this_rq,
.tasks = LIST_HEAD_INIT(env.tasks),
};
- /*
- * For NEWLY_IDLE load_balancing, we don't need to consider
- * other cpus in our group
- */
- if (idle == CPU_NEWLY_IDLE)
- env.dst_grpmask = NULL;
-
- cpumask_copy(cpus, cpu_active_mask);
+ cpumask_and(cpus, cpu_active_mask, sched_domain_span(env.sd));
schedstat_inc(sd->lb_count[idle]);
@@ -8220,7 +8213,7 @@ static int load_balance(int this_cpu, struct rq *this_rq,
/* All tasks on this runqueue were pinned by CPU affinity */
if (unlikely(env.flags & LBF_ALL_PINNED)) {
cpumask_clear_cpu(cpu_of(busiest), cpus);
- if (!cpumask_empty(cpus)) {
+ if (!cpumask_subset(cpus, env.dst_grpmask)) {
env.loop = 0;
env.loop_break = sched_nr_migrate_break;
goto redo;
next prev parent reply other threads:[~2017-05-15 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 17:01 [RFC 0/2] load_balance() fixes for affinity Jeffrey Hugo
2017-05-12 17:01 ` [RFC 1/2] sched/fair: Fix load_balance() affinity redo path Jeffrey Hugo
2017-05-12 17:23 ` Peter Zijlstra
2017-05-12 17:29 ` Jeffrey Hugo
2017-05-12 20:44 ` Peter Zijlstra
2017-05-12 20:54 ` Jeffrey Hugo
2017-05-12 20:47 ` Peter Zijlstra
2017-05-12 20:57 ` Jeffrey Hugo
2017-05-15 14:56 ` Dietmar Eggemann [this message]
2017-05-18 14:31 ` Jeffrey Hugo
2017-05-12 17:01 ` [RFC 2/2] sched/fair: Remove group imbalance from calculate_imbalance() Jeffrey Hugo
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=9b97fa6f-2b3d-3e10-fd55-208ef47f3e2a@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=austinwc@codeaurora.org \
--cc=jhugo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tbaicar@codeaurora.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