From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Jeffrey Hugo <jhugo@codeaurora.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Cc: Austin Christ <austinwc@codeaurora.org>,
Tyler Baicar <tbaicar@codeaurora.org>,
Timur Tabi <timur@codeaurora.org>
Subject: Re: [PATCH V3 1/2] sched/fair: Fix load_balance() affinity redo path
Date: Mon, 22 May 2017 10:48:59 +0100 [thread overview]
Message-ID: <b8538c14-620d-5797-762f-3287469a9991@arm.com> (raw)
In-Reply-To: <642f9111-71ae-398d-58ad-74f930533e70@arm.com>
On 19/05/17 14:31, Dietmar Eggemann wrote:
> On 18/05/17 20:36, Jeffrey Hugo wrote:
>
> [...]
>
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index d711093..a5d41b1 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -8220,7 +8220,24 @@ 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)) {
>> + /*
>> + * dst_cpu is not a valid busiest cpu in the following
>> + * check since load cannot be pulled from dst_cpu to be
>> + * put on dst_cpu.
>> + */
>> + cpumask_clear_cpu(env.dst_cpu, cpus);
>> + /*
>> + * Go back to "redo" iff the load-balance cpumask
>> + * contains other potential busiest cpus for the
>> + * current sched domain.
>> + */
>> + if (cpumask_intersects(cpus, sched_domain_span(env.sd))) {
>> + /*
>> + * Now that the check has passed, reenable
>> + * dst_cpu so that load can be calculated on
>> + * it in the redo path.
>> + */
>> + cpumask_set_cpu(env.dst_cpu, cpus);
>
> IMHO, this will work nicely and its way easier.
This was too quick ... if we still have other potential dst cpus
available and cpu_of(busiest) is the latest src cpu then this will fail.
It does work on sd with 'group_weight == 1', e.g. your MC sd 'sd->child
== NULL'.
But IMHO 'group_imbalance' propagation has to work on higher sd levels
as well.
> Another idea might be to check if the LBF_ALL_PINNED is set when we
> check if we should clean the imbalance flag.
>
> @@ -8307,14 +8307,13 @@ static int load_balance(int this_cpu, struct rq *this_rq,
> * We reach balance although we may have faced some affinity
> * constraints. Clear the imbalance flag if it was set.
> */
> - if (sd_parent) {
> + if (sd_parent && !(env.flags & LBF_ALL_PINNED)) {
> int *group_imbalance = &sd_parent->groups->sgc->imbalance;
>
> if (*group_imbalance)
> *group_imbalance = 0;
> }
[...]
next prev parent reply other threads:[~2017-05-22 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 19:36 [PATCH V3 0/2] load_balance() fixes for affinity Jeffrey Hugo
2017-05-18 19:36 ` [PATCH V3 1/2] sched/fair: Fix load_balance() affinity redo path Jeffrey Hugo
2017-05-19 13:31 ` Dietmar Eggemann
2017-05-22 9:48 ` Dietmar Eggemann [this message]
2017-05-22 19:57 ` Christ, Austin
2017-05-23 11:45 ` Dietmar Eggemann
2017-05-23 22:05 ` Jeffrey Hugo
2017-05-18 19:36 ` [PATCH V3 2/2] sched/fair: Remove group imbalance from calculate_imbalance() Jeffrey Hugo
2017-05-22 15:52 ` [PATCH V3 0/2] load_balance() fixes for affinity Peter Zijlstra
2017-05-22 20:17 ` Christ, Austin
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=b8538c14-620d-5797-762f-3287469a9991@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 \
--cc=timur@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
all inboxes | Powered by JetHome®