From: Jeffrey Hugo <jhugo@codeaurora.org>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>,
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: Thu, 18 May 2017 08:31:55 -0600 [thread overview]
Message-ID: <890e6ad4-ebe7-44dd-7369-9143d53246b1@codeaurora.org> (raw)
In-Reply-To: <9b97fa6f-2b3d-3e10-fd55-208ef47f3e2a@arm.com>
On 5/15/2017 8:56 AM, Dietmar Eggemann wrote:
> 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 ...
Hmm. I follow the idea, but I'm not too confident in the SD_OVERLAP
case, and looking at your proposed code, it seems invasive to me -
changes are needed in what would otherwise be unrelated sections of
code. I'd prefer not to go in that direction. Also, it appears that
the dst_cpu is still considered as a source for load.
We've got a different idea to address the stack issue, and still keep
the change "contained", which I'll roll into a V2 today or tomorrow.
--
Jeffrey Hugo
Qualcomm Datacenter Technologies as an affiliate of Qualcomm
Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-05-18 14:32 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
2017-05-18 14:31 ` Jeffrey Hugo [this message]
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=890e6ad4-ebe7-44dd-7369-9143d53246b1@codeaurora.org \
--to=jhugo@codeaurora.org \
--cc=austinwc@codeaurora.org \
--cc=dietmar.eggemann@arm.com \
--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