public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: rafael@kernel.org, viresh.kumar@linaro.org
Cc: linux-pm@vger.kernel.org, void@manifault.com,
	linux-kernel@vger.kernel.org, kernel-team@meta.com,
	mingo@redhat.com, peterz@infradead.org
Subject: [PATCHSET sched_ext/for-6.11] sched_ext: Integrate with schedutil
Date: Tue, 18 Jun 2024 17:12:01 -1000	[thread overview]
Message-ID: <20240619031250.2936087-1-tj@kernel.org> (raw)

sched_ext currently does not integrate with schedutil. When schedutil is the
governor, frequencies are left unregulated and usually get stuck close to
the highest performance level from running RT tasks.

This patchset integrates sched_ext with schedutil so that the BPF scheduler
can steer CPU frequencies when the schedutil governor is in use. The
implementation is straightforward. sugov_get_util() is updated to add the
BPF scheduler provided utilization metric when sched_ext is enabled.

This patchset is on top of sched_ext/for-6.11 (a5db7817af78 ("sched_ext: Add
selftests")) and contains the following two patches:

 0001-cpufreq_schedutil-Refactor-sugov_cpu_is_busy.patch
 0002-sched_ext-Add-cpuperf-support.patch

and is also available in the following git branch:

 git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git scx-cpuperf

diffstat follows. Thanks.

 kernel/sched/cpufreq_schedutil.c         |   50 +++++++++-------
 kernel/sched/ext.c                       |   83 ++++++++++++++++++++++++++
 kernel/sched/ext.h                       |    9 ++
 kernel/sched/sched.h                     |    1
 tools/sched_ext/include/scx/common.bpf.h |    3
 tools/sched_ext/scx_qmap.bpf.c           |  142 +++++++++++++++++++++++++++++++++++++++++++++-
 tools/sched_ext/scx_qmap.c               |    8 ++
 7 files changed, 270 insertions(+), 26 deletions(-)

--
tejun

             reply	other threads:[~2024-06-19  3:12 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19  3:12 Tejun Heo [this message]
2024-06-19  3:12 ` [PATCH 1/2] cpufreq_schedutil: Refactor sugov_cpu_is_busy() Tejun Heo
2024-06-19 14:07   ` Christian Loehle
2024-06-19 18:57     ` Tejun Heo
2024-06-19 19:07       ` Tejun Heo
2024-06-20  9:40         ` Christian Loehle
2024-06-19 18:45   ` Rafael J. Wysocki
2024-06-19 19:53     ` Tejun Heo
2024-06-20 17:57       ` Rafael J. Wysocki
2024-06-20 18:08         ` Tejun Heo
2024-06-21 22:38   ` Tejun Heo
2024-06-19  3:12 ` [PATCH 2/2] sched_ext: Add cpuperf support Tejun Heo
2024-06-19 14:07   ` Christian Loehle
2024-06-19 19:19     ` Tejun Heo
2024-06-19 19:51   ` [PATCH v2 " Tejun Heo
2024-06-21 22:39     ` Tejun Heo
2024-07-05 12:41     ` Vincent Guittot
2024-07-05 18:22       ` Tejun Heo
2024-07-06  9:01         ` Vincent Guittot
2024-07-07  1:44           ` Tejun Heo
2024-07-08  6:37             ` Vincent Guittot
2024-07-08 18:20               ` Tejun Heo
2024-07-08 19:51                 ` Vincent Guittot
2024-07-08 21:08                   ` Tejun Heo
2024-07-09 13:36                     ` Vincent Guittot
2024-07-09 16:43                       ` Tejun Heo
2024-07-12 10:12                         ` Vincent Guittot
2024-07-12 17:10                           ` Tejun Heo
2024-07-02 10:23   ` [PATCH " Hongyan Xia
2024-07-02 16:37     ` Tejun Heo
2024-07-02 17:12       ` Hongyan Xia
2024-07-02 17:56         ` Tejun Heo
2024-07-02 20:41           ` Hongyan Xia
2024-07-02 21:12             ` Tejun Heo
2024-07-24 23:45   ` Qais Yousef
2024-07-31  1:05     ` Tejun Heo

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=20240619031250.2936087-1-tj@kernel.org \
    --to=tj@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=void@manifault.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