From: Peter Zijlstra <peterz@infradead.org>
To: Patrick Bellasi <patrick.bellasi@arm.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Douglas Raillard <douglas.raillard@arm.com>,
Quentin Perret <quentin.perret@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Juri Lelli <juri.lelli@redhat.com>
Subject: Re: [PATCH] sched/fair: util_est: fast ramp-up EWMA on utilization increases
Date: Mon, 14 Oct 2019 16:52:18 +0200 [thread overview]
Message-ID: <20191014145218.GI2328@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190802094725.ploqfarz7fj7vrtp@e110439-lin>
The energy aware schedutil patches remimded me this was still pending.
On Fri, Aug 02, 2019 at 10:47:25AM +0100, Patrick Bellasi wrote:
> Hi Peter, Vincent,
> is there anything different I can do on this?
I think both Vincent and me are basically fine with the patch, it was
the Changelog/explanation for it that sat uneasy.
Specifically I think the 'confusion' around the PELT invariance stuff
doesn't help.
I think that if you present it simply as making util_est directly follow
upward motion and only decay on downward -- and the rationale for it --
then it should be fine.
next prev parent reply other threads:[~2019-10-14 14:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 15:05 [PATCH] sched/fair: util_est: fast ramp-up EWMA on utilization increases Patrick Bellasi
2019-06-26 11:40 ` Vincent Guittot
2019-06-28 10:08 ` Patrick Bellasi
2019-06-28 12:38 ` Peter Zijlstra
2019-06-28 13:51 ` Vincent Guittot
2019-06-28 14:10 ` Patrick Bellasi
2019-06-30 8:43 ` Vincent Guittot
2019-07-01 8:53 ` Patrick Bellasi
2019-06-28 14:00 ` Patrick Bellasi
2019-08-02 9:47 ` Patrick Bellasi
2019-10-14 14:52 ` Peter Zijlstra [this message]
2019-10-14 14:57 ` Vincent Guittot
2019-10-14 16:16 ` Douglas Raillard
2019-10-17 8:25 ` Peter Zijlstra
2019-10-21 6:19 ` Patrick Bellasi
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=20191014145218.GI2328@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dietmar.eggemann@arm.com \
--cc=douglas.raillard@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@arm.com \
--cc=quentin.perret@arm.com \
--cc=rafael.j.wysocki@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.