From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>
Cc: Qais Yousef <qyousef@layalina.io>,
Kajetan Puchalski <kajetan.puchalski@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Vincent Donnefort <vdonnefort@google.com>,
Quentin Perret <qperret@google.com>,
Abhijeet Dharmapurikar <adharmap@quicinc.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] sched: Consider CPU contention in frequency & load-balance busiest CPU selection
Date: Thu, 6 Apr 2023 17:50:29 +0200 [thread overview]
Message-ID: <20230406155030.1989554-1-dietmar.eggemann@arm.com> (raw)
This is the implementation of the idea to factor in root cfs_rq
runnable_avg as a way to consider CPU contention for CPU frequency and
`migrate_util` type load-balance busiest CPU selection.
Discussion happened under:
https://lkml.kernel.org/r/424e2c81-987d-f10e-106d-8b4c611768bc@arm.com
Dietmar Eggemann (1):
sched: Consider CPU contention in frequency & load-balance busiest CPU
selection
kernel/sched/cpufreq_schedutil.c | 3 ++-
kernel/sched/fair.c | 2 +-
kernel/sched/sched.h | 19 +++++++++++++++++++
3 files changed, 22 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2023-04-06 15:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 15:50 Dietmar Eggemann [this message]
2023-04-06 15:50 ` [PATCH 1/1] sched: Consider CPU contention in frequency & load-balance busiest CPU selection Dietmar Eggemann
2023-04-29 14:58 ` Peter Zijlstra
2023-05-03 17:13 ` Dietmar Eggemann
2023-05-04 15:23 ` Qais Yousef
2023-05-11 15:25 ` Dietmar Eggemann
2023-05-15 19:18 ` Qais Yousef
2023-05-03 16:08 ` Vincent Guittot
2023-05-04 17:11 ` Dietmar Eggemann
2023-05-05 8:22 ` Vincent Guittot
2023-05-05 18:16 ` Dietmar Eggemann
2023-05-05 7:10 ` Chen Yu
2023-05-05 18:02 ` Dietmar Eggemann
2023-05-07 2:19 ` Chen Yu
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=20230406155030.1989554-1-dietmar.eggemann@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=adharmap@quicinc.com \
--cc=kajetan.puchalski@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=qyousef@layalina.io \
--cc=vdonnefort@google.com \
--cc=vincent.guittot@linaro.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).