From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Qais Yousef <qyousef@layalina.io>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
mingo@kernel.org, peterz@infradead.org, rafael@kernel.org,
viresh.kumar@linaro.org, vschneid@redhat.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
lukasz.luba@arm.com, wvw@google.com, xuewen.yan94@gmail.com,
han.lin@mediatek.com, Jonathan.JMChen@mediatek.com
Subject: Re: [PATCH v4] sched/fair: unlink misfit task from cpu overutilized
Date: Tue, 31 Jan 2023 17:36:05 +0100 [thread overview]
Message-ID: <a5ac2767-6b15-23a2-9ebf-1aa02ee9c4f1@arm.com> (raw)
In-Reply-To: <20230129162120.ynzgsxsdjwluucmk@airbuntu>
On 29/01/2023 17:21, Qais Yousef wrote:
> On 01/26/23 12:42, Dietmar Eggemann wrote:
>> On 19/01/2023 17:42, Vincent Guittot wrote:
[...]
>> We had already this discussion whether this patch can also remove
>> Capacity Inversion (CapInv).
>>
>> After studying the code again, I'm not so sure anymore.
>>
>> This patch:
>>
>> (1) adds a dedicated return value (-1) to util_fits_cpu() when:
>>
>> `util fits 80% capacity_of() && util < uclamp_min && uclamp_min >
>> capacity_orig_thermal (region c)`
>>
>> (2) Enhancements to the CPU selection in sic() and feec() to cater for
>> this new return value.
>
> -1 means that the task fits, but only uclamp_min hint fails. ie: the task util
> is small enough to run on this cpu, but it would like to run faster and this
> cpu can't satisfy this request at the moment.
Agreed.
>> IMHO this doesn't make the intention of CapInv in util_fits_cpu()
>> obsolete, which is using:
>>
>> in CapInv:
>>
>> capacity_orig = capacity_orig_of() - thermal_load_avg
>> capacity_orig_thermal = capacity_orig_of() - thermal_load_avg
>>
>> not in CapInv:
>>
>> capacity_orig = capacity_orig_of()
>> capacity_orig_thermal = capacity_orig_of() - th_pressure
>>
>> Maybe I still miss a bit of the story?
>
> Vincent approach is different to mine. I tried to hide all the complexity in
> util_fits_cpu() so all users don't care.
>
> But with Vincent changes, now the decision is delegated to the caller to decide
> what to do if thermal pressure is causing trouble.
>
> IOW, I expect this line only stay after Vincent patch
>
> capacity_orig_thermal = capacity_orig_of() - th_pressure
OK, makes sense (for now - rework of what capacity_orig_thermal should
really be still ahead of us).
Thanks!
-- Dietmar
[...]
next prev parent reply other threads:[~2023-01-31 16:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 17:42 Vincent Guittot
2023-01-23 12:10 ` Kajetan Puchalski
2023-01-25 8:26 ` Vincent Guittot
2023-01-25 1:46 ` Kajetan Puchalski
2023-01-25 8:37 ` Vincent Guittot
2023-01-25 16:09 ` Qais Yousef
2023-01-26 11:42 ` Dietmar Eggemann
2023-01-27 16:20 ` Vincent Guittot
2023-01-31 16:36 ` Dietmar Eggemann
2023-01-29 16:21 ` Qais Yousef
2023-01-31 16:36 ` Dietmar Eggemann [this message]
2023-01-29 16:35 ` Qais Yousef
2023-01-30 14:13 ` Vincent Guittot
2023-01-30 19:30 ` Qais Yousef
2023-01-31 15:38 ` Vincent Guittot
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=a5ac2767-6b15-23a2-9ebf-1aa02ee9c4f1@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=Jonathan.JMChen@mediatek.com \
--cc=han.lin@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=rafael@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=vschneid@redhat.com \
--cc=wvw@google.com \
--cc=xuewen.yan94@gmail.com \
/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®