From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Qais Yousef <qyousef@layalina.io>,
Vincent Guittot <vincent.guittot@linaro.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Qais Yousef <qais.yousef@arm.com>
Subject: Re: [PATCH] sched/fair: Check a task has a fitting cpu when updating misfit
Date: Mon, 4 Sep 2023 15:18:20 +0200 [thread overview]
Message-ID: <2562890e-e824-7721-8dbe-8c5ae6ac42a9@arm.com> (raw)
In-Reply-To: <20230829153524.iswwflqd3iw3uybx@airbuntu>
On 29/08/2023 17:35, Qais Yousef wrote:
> On 08/29/23 16:10, Vincent Guittot wrote:
>> On Sun, 20 Aug 2023 at 22:34, Qais Yousef <qyousef@layalina.io> wrote:
[...]
>>> kernel/sched/fair.c | 50 ++++++++++++++++++++++++++++++++++++++-------
>>> 1 file changed, 43 insertions(+), 7 deletions(-)
>>>
>>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>>> index 0b7445cd5af9..f08c5f3bf895 100644
>>> --- a/kernel/sched/fair.c
>>> +++ b/kernel/sched/fair.c
>>> @@ -4853,17 +4853,50 @@ static inline int task_fits_cpu(struct task_struct *p, int cpu)
>>>
>>> static inline void update_misfit_status(struct task_struct *p, struct rq *rq)
>>> {
>>> + unsigned long uclamp_min, uclamp_max;
>>> + unsigned long util, cap_level;
>>> + bool has_fitting_cpu = false;
>>> + int cpu = cpu_of(rq);
>>> +
>>> if (!sched_asym_cpucap_active())
>>> return;
>>>
>>> - if (!p || p->nr_cpus_allowed == 1) {
>>> - rq->misfit_task_load = 0;
>>> - return;
>>> - }
>>> + if (!p || p->nr_cpus_allowed == 1)
>>> + goto out;
>>>
>>> - if (task_fits_cpu(p, cpu_of(rq))) {
>>> - rq->misfit_task_load = 0;
>>> - return;
>>> + uclamp_min = uclamp_eff_value(p, UCLAMP_MIN);
>>> + uclamp_max = uclamp_eff_value(p, UCLAMP_MAX);
>>> + util = task_util_est(p);
>>> +
>>> + if (util_fits_cpu(util, uclamp_min, uclamp_max, cpu) > 0)
>>> + goto out;
util_fits_cpu() checks fits_capacity(util, capacity_of(cpu)) but the
capacity pressure could change between update_misfit_status() and CFS lb?
>>> +
>>> + cap_level = capacity_orig_of(cpu);
>>> +
>>> + /* If we can't fit the biggest CPU, that's the best we can ever get. */
>>> + if (cap_level == SCHED_CAPACITY_SCALE)
>>> + goto out;
>>> +
>>> + /*
>>> + * If the task affinity is not set to default, make sure it is not
>>> + * restricted to a subset where no CPU can ever fit it. Triggering
>>> + * misfit in this case is pointless as it has no where better to move
>>> + * to. And it can lead to balance_interval to grow too high as we'll
>>> + * continuously fail to move it anywhere.
>>> + */
>>> + if (!cpumask_equal(p->cpus_ptr, cpu_possible_mask)) {
>>> + for_each_cpu(cpu, p->cpus_ptr) {
>>
>> I haven't looked at the problem in detail and at other possibilities
>> so far but for_each_cpu doesn't scale and update_misfit_status() being
>> called in pick_next_task_fair() so you must find another way to detect
>> this
>
> Okay, will do.
We have LIST_HEAD(asym_cap_list) (list of cpumasks according to
cpu_capacity_orig CPU groups) in kernel/sched/topology.c to set
SD_ASYM_CPUCAPACITY{,_FULL} for asymmetric CPU capacity systems.
Maybe this could be made usable in fair.c as well?
But checking via util_fits_cpu() wouldn't work then since it's per-CPU.
The check of p's CPU affinity, its uclamped util_avg value and the
cpu_capacity_orig is sufficient here. Then using those cpumasks could work.
next prev parent reply other threads:[~2023-09-04 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-20 20:34 Qais Yousef
2023-08-29 14:10 ` Vincent Guittot
2023-08-29 15:35 ` Qais Yousef
2023-09-04 13:18 ` Dietmar Eggemann [this message]
2023-09-04 19:38 ` Qais Yousef
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=2562890e-e824-7721-8dbe-8c5ae6ac42a9@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=qyousef@layalina.io \
--cc=vincent.guittot@linaro.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®