From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>,
peterz@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org
Cc: rjw@rjwysocki.net, Morten.Rasmussen@arm.com,
patrick.bellasi@arm.com, pjt@google.com, bsegall@google.com,
thara.gopinath@linaro.org, pkondeti@codeaurora.org,
quentin.perret@arm.com
Subject: Re: [PATCH v6 0/2] sched/fair: update scale invariance of PELT
Date: Mon, 12 Nov 2018 18:58:13 -0800 [thread overview]
Message-ID: <e873dfbb-d13e-93c7-251e-dea90c3b40b5@arm.com> (raw)
In-Reply-To: <1541780454-9934-1-git-send-email-vincent.guittot@linaro.org>
On 11/9/18 8:20 AM, Vincent Guittot wrote:
> This new version of the scale invariance patchset adds an important change
> compare to v3 and before. It still scales the time to reflect the
> amount of work that has been done during the elapsed running time but this is
> now done at rq level instead of per entity and rt/dl/cfs_rq. The main
> advantage is that it is done once per clock update and we don't need to
> maintain per sched_avg's stolen_idle_time anymore. This also ensures that
> all pelt signals will be always synced for a rq.
>
> The 1st patch makes available rq_of() helper function for pelt.c file and
> the 2nd patch implements the new scaling algorithm
>
> Changes since v5:
> - Fix running_sum scaling in update_tg_cfs_runnable() raised by Dietmar
> - Remove unused cpu parameters raised by Dietmar
I just re-discovered ... the comment for the definition of struct
sched_avg in include/linux/sched.h also mentioned the different ways how
we do invariance for load_avg and util_avg.
[...]
prev parent reply other threads:[~2018-11-13 2:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 16:20 [PATCH v6 0/2] sched/fair: update scale invariance of PELT Vincent Guittot
2018-11-09 16:20 ` [PATCH v6 1/2] sched/fair: move rq_of helper function Vincent Guittot
2018-11-09 16:20 ` [PATCH v6 2/2] sched/fair: update scale invariance of PELT Vincent Guittot
2018-11-13 2:53 ` Dietmar Eggemann
2018-11-14 23:56 ` Vincent Guittot
2018-11-13 2:58 ` Dietmar Eggemann [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=e873dfbb-d13e-93c7-251e-dea90c3b40b5@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=Morten.Rasmussen@arm.com \
--cc=bsegall@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=pkondeti@codeaurora.org \
--cc=quentin.perret@arm.com \
--cc=rjw@rjwysocki.net \
--cc=thara.gopinath@linaro.org \
--cc=vincent.guittot@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).