linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Guittot <vincent.guittot@linaro.org>
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
	dietmar.eggemann@arm.com, rostedt@goodmis.org,
	bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
	vschneid@redhat.com, rafael@kernel.org, viresh.kumar@linaro.org,
	qyousef@layalina.io, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Cc: lukasz.luba@arm.com, wyes.karny@amd.com, beata.michalska@arm.com,
	Vincent Guittot <vincent.guittot@linaro.org>
Subject: [PATCH v4 0/2] Rework interface between scheduler and schedutil governor
Date: Wed, 22 Nov 2023 14:39:02 +0100	[thread overview]
Message-ID: <20231122133904.446032-1-vincent.guittot@linaro.org> (raw)

Following the discussion with Qais [1] about how to handle uclamp
requirements and after syncing with him, we agreed that I should move
forward on the patchset to rework the interface between scheduler and
schedutil governor to provide more information to the latter. Scheduler
(and EAS in particular) doesn't need anymore to guess estimate which
headroom the governor wants to apply and will directly ask for the target
freq. Then the governor directly gets the actual utilization and new
minimum and maximum boundaries to select this target frequency and
doesn't have to deal anymore with scheduler internals like uclamp when
including iowait boost.

[1] https://lore.kernel.org/lkml/CAKfTPtA5JqNCauG-rP3wGfq+p8EEVx9Tvwj6ksM3SYCwRmfCTg@mail.gmail.com/

Changes since v3:
- Fix freq selection with runnable RT

Changes since v2:
- remove useless target variable

Changes since v1:
- fix a bug (always set max even when returning early)
- fix typos
  
Vincent Guittot (2):
  sched/schedutil: Rework performance estimation
  sched/schedutil: Rework iowait boost

 include/linux/energy_model.h     |  1 -
 kernel/sched/core.c              | 90 ++++++++++++++------------------
 kernel/sched/cpufreq_schedutil.c | 64 ++++++++++++++---------
 kernel/sched/fair.c              | 22 ++++++--
 kernel/sched/sched.h             | 84 +++--------------------------
 5 files changed, 103 insertions(+), 158 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-11-22 13:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 13:39 Vincent Guittot [this message]
2023-11-21 22:36 ` [PATCH v4 0/2] Rework interface between scheduler and schedutil governor Qais Yousef
2023-11-22 13:39 ` [PATCH v4 1/2] sched/schedutil: Rework performance estimation Vincent Guittot
2023-11-22 13:49   ` Rafael J. Wysocki
2023-11-23 10:54   ` [tip: sched/core] sched/cpufreq: Rework schedutil governor " tip-bot2 for Vincent Guittot
2023-11-22 13:39 ` [PATCH v4 2/2] sched/schedutil: Rework iowait boost Vincent Guittot
2023-11-22 13:51   ` Rafael J. Wysocki
2023-11-23 10:34     ` Ingo Molnar
2023-11-23 10:54   ` [tip: sched/core] sched/cpufreq: " tip-bot2 for 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=20231122133904.446032-1-vincent.guittot@linaro.org \
    --to=vincent.guittot@linaro.org \
    --cc=beata.michalska@arm.com \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=qyousef@layalina.io \
    --cc=rafael@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=viresh.kumar@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=wyes.karny@amd.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;
as well as URLs for NNTP newsgroup(s).