From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Chen Yu <yu.c.chen@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>,
Swapnil Sapkal <Swapnil.Sapkal@amd.com>,
Aaron Lu <aaron.lu@intel.com>, Tim Chen <tim.c.chen@intel.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
"Gautham R . Shenoy" <gautham.shenoy@amd.com>,
x86@kernel.org
Subject: Re: [RFC PATCH 1/2] sched/fair: Introduce UTIL_FITS_CAPACITY feature
Date: Thu, 19 Oct 2023 10:49:09 -0400 [thread overview]
Message-ID: <6bb3bfe5-13d6-413a-bf31-cec5596757f2@efficios.com> (raw)
In-Reply-To: <25e778e2-d91a-4f4d-9f6b-ff144eab3211@efficios.com>
On 2023-10-19 09:28, Mathieu Desnoyers wrote:
> On 2023-10-19 07:35, Chen Yu wrote:
[...]
>>> +/*
>>> + * Returns true if adding the task utilization to the estimated
>>> + * utilization of the runnable tasks on @cpu does not exceed the
>>> + * capacity of @cpu.
>>> + *
>>> + * This considers only the utilization of _runnable_ tasks on the @cpu
>>> + * runqueue, excluding blocked and sleeping tasks. This is achieved by
>>> + * using the runqueue util_est.enqueued, and by estimating the capacity
>>> + * of @cpu based on arch_scale_cpu_capacity and
>>> arch_scale_thermal_pressure
>>> + * rather than capacity_of() because capacity_of() considers
>>> + * blocked/sleeping tasks in other scheduler classes.
>>> + *
>>> + * The utilization vs capacity comparison is done without the margin
>>> + * provided by fits_capacity(), because fits_capacity() is used to
>>> + * validate whether the utilization of a task fits within the overall
>>> + * capacity of a cpu, whereas this function validates whether the task
>>> + * utilization fits within the _remaining_ capacity of the cpu,
>>> which is
>>> + * more precise.
>>> + */
>>> +static inline bool task_fits_remaining_cpu_capacity(unsigned long
>>> task_util,
>>> + int cpu)
>>> +{
>>> + unsigned long total_util, capacity;
>>> +
>>> + if (!sched_util_fits_capacity_active())
>>> + return false;
>>> + total_util = READ_ONCE(cpu_rq(cpu)->cfs.avg.util_est.enqueued) +
>>> task_util;
>>> + capacity = arch_scale_cpu_capacity(cpu) -
>>> arch_scale_thermal_pressure(cpu);
>>
>> scale_rt_capacity(cpu) could provide the remaining cpu capacity after
>> substracted by
>> the side activity(rt tasks/thermal pressure/irq time), maybe it would
>> be more accurate?
>
> AFAIU, scale_rt_capacity(cpu) works similarly to capacity_of(cpu) and
> considers blocked and sleeping tasks in the rq->avg_rt.util_avg and
> rq->avg_dl.util_avg. I'm not sure sure about rq->avg_irq.util_avg and
> thermal_load_avg().
>
> This goes against what is needed here: we need a utilization that only
> considers enqueued runnable tasks (exluding blocked and sleeping tasks).
> Or am I missing something ?
>
I was wrong. Looking more closely at dl and rt sched classes, unlike the
fair sched class, they don't appear to take into account
sleeping/blocked tasks in their util_avg. They just accumulate the rq
util_sum and derive a rq util_avg from it. Likewise for thermal and irq.
So both capacity_of(cpu) and scale_rt_capacity(cpu) would appear to do
what we need here, but AFAIU capacity_of(cpu) is based on a metric which
is only updated once per jiffy or so.
Let me try using scale_rt_capacity(cpu) then.
Thanks!
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2023-10-19 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 20:45 [RFC PATCH 0/2] sched/fair migration reduction features Mathieu Desnoyers
2023-10-18 20:45 ` [RFC PATCH 1/2] sched/fair: Introduce UTIL_FITS_CAPACITY feature Mathieu Desnoyers
2023-10-19 11:35 ` Chen Yu
2023-10-19 13:28 ` Mathieu Desnoyers
2023-10-19 14:49 ` Mathieu Desnoyers [this message]
2023-10-18 20:45 ` [RFC PATCH 2/2] sched/fair: Introduce SELECT_BIAS_PREV to reduce migrations Mathieu Desnoyers
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=6bb3bfe5-13d6-413a-bf31-cec5596757f2@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=Swapnil.Sapkal@amd.com \
--cc=aaron.lu@intel.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=gautham.shenoy@amd.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tim.c.chen@intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=x86@kernel.org \
--cc=yu.c.chen@intel.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®