From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Pierre Gondois <pierre.gondois@arm.com>, linux-kernel@vger.kernel.org
Cc: Qais Yousef <qyousef@layalina.io>,
Vincent Guittot <vincent.guittot@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>
Subject: Re: [PATCH v2] sched/fair: Use all little CPUs for CPU-bound workload
Date: Wed, 29 Nov 2023 13:16:30 +0100 [thread overview]
Message-ID: <764e015b-b987-4722-b088-56da22848644@arm.com> (raw)
In-Reply-To: <980a1a52-80a1-4d3b-8931-5f9a6546bbf5@arm.com>
On 29/11/2023 11:48, Pierre Gondois wrote:
>
>
> On 11/29/23 09:55, Dietmar Eggemann wrote:
>> On 24/11/2023 16:33, Pierre Gondois wrote:
[...]
>>> Testing workload ([1]):
>>> Spawn 6 CPU-bound tasks. During the first 100ms (step 1), each tasks
>>> is affine to a CPU, except for:
>>> - one little CPU which is left idle.
>>> - one big CPU which has 2 tasks affine.
>>> After the 100ms (step 2), remove the cpumask affinity.
>>>
>>> Before patch:
>>> During step 2, the load balancer running from the idle CPU tags sched
>>> domains as:
>>> - little CPUs: 'group_has_spare'. Indeed, 3 CPU-bound tasks run on a
>>> 4 CPUs sched-domain, and the idle CPU provides enough spare
>>> capacity.
>>
>> What is meant by 'idle CPU provides enough spare capacity? I thought the
>> task (util_avg ~ 512_ does not fit on the sched group [1,3-5] when we
>> consider util_avg/capacity (383)
>
> Right, I meant that when evaluating the 'group_type', there is enough spare
> capacity when summing the utilization of CPUs in the the MC sched domain:
>
> ---
> group_has_capacity()
> {
> [...]
> if ((sgs->group_capacity * 100) >
> (sgs->group_util * imbalance_pct))
> return true;
> [...]
> }
I see. But doesn't group_has_capacity() already return true because of
`if (sgs->sum_nr_running < sgs->group_weight)` in this case (3 < 4)?
Maybe you can make this clearer when sending the v3 with the Reviewed-By
tags?
> ---
>
>>
>> The calculated imbalance of ~350 is too small for the task-size and
>> that's why we need the 'shr_bound(util, env->sd->nr_balance_failed)' to
>> let the task load-balance if nr_balance_failed = 2?
>
> Yes exact, the tasks are too big and cannot fit this imbalance value
> (representing the available spare capacity in the little CPUs in this
> case).
>
> 'shr_bound(...)' allows to progressively reduce the size of the tasks and
> allow migrations after having tried to balance 'nr_balance_failed' times.
[...]
next prev parent reply other threads:[~2023-11-29 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 15:33 Pierre Gondois
2023-11-24 15:56 ` Vincent Guittot
2023-11-29 8:55 ` Dietmar Eggemann
2023-11-29 10:48 ` Pierre Gondois
2023-11-29 12:16 ` Dietmar Eggemann [this message]
2023-11-30 17:30 ` 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=764e015b-b987-4722-b088-56da22848644@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pierre.gondois@arm.com \
--cc=qyousef@layalina.io \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®