From: Peter Zijlstra <peterz@infradead.org>
To: Douglas RAILLARD <douglas.raillard@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
mingo@redhat.com, rjw@rjwysocki.net, viresh.kumar@linaro.org,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
dietmar.eggemann@arm.com, qperret@qperret.net,
patrick.bellasi@matbug.net, dh.han@samsung.com
Subject: Re: [RFC PATCH v3 0/6] sched/cpufreq: Make schedutil energy aware
Date: Mon, 14 Oct 2019 16:53:15 +0200 [thread overview]
Message-ID: <20191014145315.GZ2311@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20191011134500.235736-1-douglas.raillard@arm.com>
On Fri, Oct 11, 2019 at 02:44:54PM +0100, Douglas RAILLARD wrote:
> This has been ligthly tested with a rtapp task ramping from 10% to 75%
> utilisation on a big core. Results are improved by fast ramp-up
> EWMA [1], since it greatly reduces the oscillation in frequency at first
> idle when ramping up.
>
> [1] [PATCH] sched/fair: util_est: fast ramp-up EWMA on utilization increases
> Message-ID: <20190620150555.15717-1-patrick.bellasi@arm.com>
> https://lore.kernel.org/lkml/20190620150555.15717-1-patrick.bellasi@arm.com/
I don't really see anything fundamentally weird here. Any actual numbers
or other means of quantifying the improvement these patches bring?
next prev parent reply other threads:[~2019-10-14 14:53 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 13:44 [RFC PATCH v3 0/6] sched/cpufreq: Make schedutil energy aware Douglas RAILLARD
2019-10-11 13:44 ` [RFC PATCH v3 1/6] PM: Introduce em_pd_get_higher_freq() Douglas RAILLARD
2019-10-17 8:57 ` Dietmar Eggemann
2019-10-17 9:58 ` Dietmar Eggemann
2019-10-17 11:09 ` Douglas Raillard
2019-10-11 13:44 ` [RFC PATCH v3 2/6] sched/cpufreq: Attach perf domain to sugov policy Douglas RAILLARD
2019-10-17 8:57 ` Dietmar Eggemann
2019-10-17 10:22 ` Douglas Raillard
2019-10-11 13:44 ` [RFC PATCH v3 3/6] sched/cpufreq: Hook em_pd_get_higher_power() into get_next_freq() Douglas RAILLARD
2019-10-11 13:44 ` [RFC PATCH v3 4/6] sched/cpufreq: Introduce sugov_cpu_ramp_boost Douglas RAILLARD
2019-10-14 14:33 ` Peter Zijlstra
2019-10-14 15:32 ` Douglas Raillard
2019-10-17 8:57 ` Dietmar Eggemann
2019-10-17 11:19 ` Douglas Raillard
2019-10-11 13:44 ` [RFC PATCH v3 5/6] sched/cpufreq: Boost schedutil frequency ramp up Douglas RAILLARD
2019-10-17 9:21 ` Dietmar Eggemann
2019-10-11 13:45 ` [RFC PATCH v3 6/6] sched/cpufreq: Add schedutil_em_tp tracepoint Douglas RAILLARD
2019-10-14 14:53 ` Peter Zijlstra [this message]
2019-10-14 15:50 ` [RFC PATCH v3 0/6] sched/cpufreq: Make schedutil energy aware Douglas Raillard
2019-10-17 9:50 ` Peter Zijlstra
2019-10-17 11:11 ` Quentin Perret
2019-10-17 14:11 ` Peter Zijlstra
2019-10-18 7:44 ` Dietmar Eggemann
2019-10-18 7:59 ` Peter Zijlstra
2019-10-18 17:24 ` Douglas Raillard
2019-10-18 8:11 ` Peter Zijlstra
2019-10-17 14:23 ` Douglas Raillard
2019-10-17 14:53 ` Peter Zijlstra
2019-10-17 19:07 ` Peter Zijlstra
2019-10-18 11:46 ` Douglas Raillard
2019-10-18 12:07 ` Peter Zijlstra
2019-10-18 14:44 ` Douglas Raillard
2019-10-18 15:15 ` Vincent Guittot
2019-10-18 16:03 ` Douglas Raillard
2019-10-18 15:20 ` Vincent Guittot
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=20191014145315.GZ2311@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dh.han@samsung.com \
--cc=dietmar.eggemann@arm.com \
--cc=douglas.raillard@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=patrick.bellasi@matbug.net \
--cc=qperret@qperret.net \
--cc=rjw@rjwysocki.net \
--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).