From: Morten Rasmussen <morten.rasmussen@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vincent Guittot <vincent.guittot@linaro.org>,
dietmar.eggemann@arm.com, patrick.bellasi@matbug.net,
lenb@kernel.org, linux-kernel@vger.kernel.org,
valentin.schneider@arm.com, ionela.voinescu@arm.com,
qperret@google.com, viresh.kumar@linaro.org
Subject: Re: [RFC] Documentation/scheduler/schedutil.txt
Date: Fri, 20 Nov 2020 15:37:55 +0100 [thread overview]
Message-ID: <20201120143715.GA3456@e123083-lin> (raw)
In-Reply-To: <20201120075527.GB2414@hirez.programming.kicks-ass.net>
Hi Peter,
Looks like a nice summary to me.
On Fri, Nov 20, 2020 at 08:55:27AM +0100, Peter Zijlstra wrote:
> Hi,
>
> I was recently asked to explain how schedutil works, the below write-up
> is the result of that and I figured we might as well stick it in the
> tree.
>
> Not as a patch for easy reading and commenting.
>
> ---
>
> NOTE; all this assumes a linear relation between frequency and work capacity,
> we know this is flawed, but it is the best workable approximation.
If you replace frequency with performance level everywhere (CPPC style),
most of it should still work without that assumption. The assumption
might have be made in hw or fw instead though.
Morten
next prev parent reply other threads:[~2020-11-20 14:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 7:55 [RFC] Documentation/scheduler/schedutil.txt Peter Zijlstra
2020-11-20 8:56 ` Peter Zijlstra
2020-11-20 9:13 ` Quentin Perret
2020-11-20 9:19 ` Viresh Kumar
2020-11-20 9:27 ` Quentin Perret
2020-11-23 9:30 ` Dietmar Eggemann
2020-11-23 10:05 ` Vincent Guittot
2020-11-23 11:27 ` Dietmar Eggemann
2020-11-23 13:42 ` Vincent Guittot
2020-11-23 18:39 ` Dietmar Eggemann
2020-11-20 11:45 ` Valentin Schneider
2020-11-20 14:37 ` Morten Rasmussen [this message]
2020-11-23 9:26 ` Dietmar Eggemann
2020-11-23 14:51 ` Peter Zijlstra
2020-12-02 14:18 ` Mel Gorman
2020-12-02 15:54 ` Peter Zijlstra
2020-12-02 16:45 ` Mel Gorman
2020-12-02 16:58 ` Peter Zijlstra
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=20201120143715.GA3456@e123083-lin \
--to=morten.rasmussen@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=patrick.bellasi@matbug.net \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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