From: Vincent Guittot <vincent.guittot@linaro.org>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: linux@armlinux.org.uk, catalin.marinas@arm.com, will@kernel.org,
sudeep.holla@arm.com, rafael@kernel.org,
viresh.kumar@linaro.org, agross@kernel.org,
andersson@kernel.org, konrad.dybcio@linaro.org,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com, vschneid@redhat.com, lukasz.luba@arm.com,
rui.zhang@intel.com, mhiramat@kernel.org,
daniel.lezcano@linaro.org, amit.kachhap@gmail.com,
corbet@lwn.net, gregkh@linuxfoundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
qyousef@layalina.io
Subject: Re: [PATCH v3 0/5] Rework system pressure interface to the scheduler
Date: Tue, 9 Jan 2024 14:29:31 +0100 [thread overview]
Message-ID: <CAKfTPtAOSgnStDSao1QarHuUW9BTfk1o7r6NO4LhwEJMhq1drg@mail.gmail.com> (raw)
In-Reply-To: <d37e3d06-d9fc-4fc3-ad92-e7031489660a@arm.com>
On Tue, 9 Jan 2024 at 12:34, Dietmar Eggemann <dietmar.eggemann@arm.com> wrote:
>
> On 08/01/2024 14:48, Vincent Guittot wrote:
> > Following the consolidation and cleanup of CPU capacity in [1], this serie
> > reworks how the scheduler gets the pressures on CPUs. We need to take into
> > account all pressures applied by cpufreq on the compute capacity of a CPU
> > for dozens of ms or more and not only cpufreq cooling device or HW
> > mitigiations. we split the pressure applied on CPU's capacity in 2 parts:
> > - one from cpufreq and freq_qos
> > - one from HW high freq mitigiation.
> >
> > The next step will be to add a dedicated interface for long standing
> > capping of the CPU capacity (i.e. for seconds or more) like the
> > scaling_max_freq of cpufreq sysfs. The latter is already taken into
> > account by this serie but as a temporary pressure which is not always the
> > best choice when we know that it will happen for seconds or more.
>
> I guess this is related to the 'user space system pressure' (*) slide of
> your OSPM '23 talk.
yes
>
> Where do you draw the line when it comes to time between (*) and the
> 'medium pace system pressure' (e.g. thermal and FREQ_QOS).
My goal is to consider the /sys/../scaling_max_freq as the 'user space
system pressure'
>
> IIRC, with (*) you want to rebuild the sched domains etc.
The easiest way would be to rebuild the sched_domain but the cost is
not small so I would prefer to skip the rebuild and add a new signal
that keep track on this capped capacity
>
> >
> > [1] https://lore.kernel.org/lkml/20231211104855.558096-1-vincent.guittot@linaro.org/
> >
> > Change since v1:
> > - Rework cpufreq_update_pressure()
> >
> > Change since v1:
> > - Use struct cpufreq_policy as parameter of cpufreq_update_pressure()
> > - Fix typos and comments
> > - Make sched_thermal_decay_shift boot param as deprecated
> >
> > Vincent Guittot (5):
> > cpufreq: Add a cpufreq pressure feedback for the scheduler
> > sched: Take cpufreq feedback into account
> > thermal/cpufreq: Remove arch_update_thermal_pressure()
> > sched: Rename arch_update_thermal_pressure into
> > arch_update_hw_pressure
> > sched/pelt: Remove shift of thermal clock
> >
> > .../admin-guide/kernel-parameters.txt | 1 +
> > arch/arm/include/asm/topology.h | 6 +-
> > arch/arm64/include/asm/topology.h | 6 +-
> > drivers/base/arch_topology.c | 26 ++++----
> > drivers/cpufreq/cpufreq.c | 36 +++++++++++
> > drivers/cpufreq/qcom-cpufreq-hw.c | 4 +-
> > drivers/thermal/cpufreq_cooling.c | 3 -
> > include/linux/arch_topology.h | 8 +--
> > include/linux/cpufreq.h | 10 +++
> > include/linux/sched/topology.h | 8 +--
> > .../{thermal_pressure.h => hw_pressure.h} | 14 ++---
> > include/trace/events/sched.h | 2 +-
> > init/Kconfig | 12 ++--
> > kernel/sched/core.c | 8 +--
> > kernel/sched/fair.c | 63 +++++++++----------
> > kernel/sched/pelt.c | 18 +++---
> > kernel/sched/pelt.h | 16 ++---
> > kernel/sched/sched.h | 22 +------
> > 18 files changed, 144 insertions(+), 119 deletions(-)
> > rename include/trace/events/{thermal_pressure.h => hw_pressure.h} (55%)
>
next prev parent reply other threads:[~2024-01-09 13:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 13:48 [PATCH v3 0/5] Rework system pressure interface to the scheduler Vincent Guittot
2024-01-08 13:48 ` [PATCH v3 1/5] cpufreq: Add a cpufreq pressure feedback for " Vincent Guittot
2024-01-08 16:35 ` Dietmar Eggemann
2024-01-08 16:46 ` Vincent Guittot
2024-01-09 11:24 ` Vincent Guittot
2024-01-08 13:48 ` [PATCH v3 2/5] sched: Take cpufreq feedback into account Vincent Guittot
2024-01-09 11:22 ` Dietmar Eggemann
2024-01-09 14:30 ` Vincent Guittot
2024-01-10 13:51 ` Dietmar Eggemann
2024-01-10 17:25 ` Vincent Guittot
2024-01-08 13:48 ` [PATCH v3 3/5] thermal/cpufreq: Remove arch_update_thermal_pressure() Vincent Guittot
2024-01-08 13:48 ` [PATCH v3 4/5] sched: Rename arch_update_thermal_pressure into arch_update_hw_pressure Vincent Guittot
2024-01-09 11:56 ` Dietmar Eggemann
2024-01-09 13:33 ` Vincent Guittot
2024-01-08 13:48 ` [PATCH v3 5/5] sched/pelt: Remove shift of thermal clock Vincent Guittot
2024-01-09 11:33 ` [PATCH v3 0/5] Rework system pressure interface to the scheduler Dietmar Eggemann
2024-01-09 13:29 ` Vincent Guittot [this message]
2024-01-10 18:10 ` Dietmar Eggemann
2024-01-19 17:57 ` 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=CAKfTPtAOSgnStDSao1QarHuUW9BTfk1o7r6NO4LhwEJMhq1drg@mail.gmail.com \
--to=vincent.guittot@linaro.org \
--cc=agross@kernel.org \
--cc=amit.kachhap@gmail.com \
--cc=andersson@kernel.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=juri.lelli@redhat.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukasz.luba@arm.com \
--cc=mgorman@suse.de \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rui.zhang@intel.com \
--cc=sudeep.holla@arm.com \
--cc=viresh.kumar@linaro.org \
--cc=vschneid@redhat.com \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).