From: Peter Zijlstra <peterz@infradead.org>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vincent Guittot <vincent.guittot@linaro.org>,
Morten Rasmussen <morten.rasmussen@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: Mon, 23 Nov 2020 15:51:28 +0100 [thread overview]
Message-ID: <20201123145128.GS3021@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <31ab5111-8cea-3a95-823e-f3a84476f7d6@arm.com>
On Mon, Nov 23, 2020 at 10:26:13AM +0100, Dietmar Eggemann wrote:
> On 20/11/2020 08:55, Peter Zijlstra wrote:
>
> [...]
>
> > PELT (Per Entity Load Tracking)
> > -------------------------------
>
> [...]
>
> > Using this we track 2 key metrics: 'running' and 'runnable'. 'Running'
> > reflects the time an entity spends on the CPU, while 'runnable' reflects the
> > time an entity spends on the runqueue. When there is only a single task these
> > two metrics are the same, but once there is contention for the CPU 'running'
> > will decrease to reflect the fraction of time each task spends on the CPU
> > while 'runnable' will increase to reflect the amount of contention.
>
> People might find it confusing to map 'running and 'runnable' into the 3
> PELT signals (load_avg, runnable_avg and util_avg) being used in the
> scheduler ... with load_avg being 'runnable' and 'weight' based.
Yeah, but that's for another document, I suppose. much of pelt.c uses
runnable. Also, the comment that goes with struct sched_avg should
explain.
> > For more detail see: kernel/sched/pelt.c
> >
> >
> > Frequency- / Heterogeneous Invariance
> > -------------------------------------
>
> We call 'Heterogeneous Invariance' CPU invariance in chapter 2.3
> Documentation/scheduler/sched-capacity.rst.
>
> [...]
Fair enough; I've renamed it to match.
> > For more detail see:
> >
> > - kernel/sched/pelt.h:update_rq_clock_pelt()
> > - arch/x86/kernel/smpboot.c:"APERF/MPERF frequency ratio computation."
>
> drivers/base/arch_topology.c:"f_cur/f_max ratio computation".
I can't seem to find that in any tree near me (I tried tip/master and
next/master)
> > UTIL_EST / UTIL_EST_FASTUP
> > --------------------------
>
> [...]
>
> > util_est := \Sum_t max( t_running, t_util_est_ewma )
> >
> > For more detail see: kernel/sched/fair.h:util_est_dequeue()
>
> s/fair.h/fair.c
>
> > UCLAMP
> > ------
> >
> > It is possible to set effective u_min and u_max clamps on each task; the
>
> s/on each task/on each CFS or RT task
Thanks!
next prev parent reply other threads:[~2020-11-23 14:52 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
2020-11-23 9:26 ` Dietmar Eggemann
2020-11-23 14:51 ` Peter Zijlstra [this message]
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=20201123145128.GS3021@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=morten.rasmussen@arm.com \
--cc=patrick.bellasi@matbug.net \
--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;
as well as URLs for NNTP newsgroup(s).