From: Peter Zijlstra <peterz@infradead.org>
To: Mel Gorman <mgorman@suse.de>
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>,
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: Wed, 2 Dec 2020 17:58:28 +0100 [thread overview]
Message-ID: <20201202165828.GC2414@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20201202164531.GA3306@suse.de>
On Wed, Dec 02, 2020 at 04:45:31PM +0000, Mel Gorman wrote:
> > > It's less obvious what the consequence is unless the reader manages to
> > > tie the IO-wait comment in "Schedutil / DVFS" to this section.
> >
> > I'm not entirely sure I follow. The purpose of UTIL_EST is to avoid
> > ramp-up issues and isn't related to IO-wait boosting.
> >
>
> I mixed up the example. Historically io-wait boosting was one way of
> avoiding DVFS ramp-up issues but now that I reread it, it's best to leave
> it general like you already have in your current version.
So IO-wait boosting is an interesting case; as it captures something not
present in the rest of the model, namely interaction.
There's also that series of patches that does the cpu/gpu interaction
thing.
It would be worth expanding on it, but I didn't have it in me to dig
through the archives to get a coherent description of the current state
of things. Something left todo later...
prev parent reply other threads:[~2020-12-02 16:59 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
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 [this message]
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=20201202165828.GC2414@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=mgorman@suse.de \
--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