From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Jian-Min Liu <jian-min.liu@mediatek.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Vincent Donnefort <vdonnefort@google.com>
Cc: Quentin Perret <qperret@google.com>,
Patrick Bellasi <patrick.bellasi@matbug.net>,
Abhijeet Dharmapurikar <adharmap@quicinc.com>,
Qais Yousef <qais.yousef@arm.com>,
linux-kernel@vger.kernel.org,
Jonathan JMChen <jonathan.jmchen@mediatek.com>,
Kajetan Puchalski <kajetan.puchalski@arm.com>
Subject: Re: [RFC PATCH 0/1] sched/pelt: Change PELT halflife at runtime
Date: Wed, 28 Sep 2022 19:09:40 +0200 [thread overview]
Message-ID: <ef5fcbf2-e018-9af2-48c3-9fea3109b27f@arm.com> (raw)
In-Reply-To: <0f82011994be68502fd9833e499749866539c3df.camel@mediatek.com>
+ Kajetan Puchalski <kajetan.puchalski@arm.com>
On 20/09/2022 16:07, Jian-Min Liu wrote:
>
> Update some test data in android phone to support switching PELT HL
> is helpful functionality.
>
> We switch runtime PELT HL during runtime by difference scenario e.g.
> pelt8 in playing game, pelt32 in camera video. Support runntime
> switching PELT HL is flexible for different workloads.
>
> the below table show performance & power data points:
>
> ---------------------------------------------------------------------
> --| | PELT
> halflife |
> | |----------------------------------------------|
> | | 32 | 16 | 8 |
> | |----------------------------------------------|
> | | avg min avg | avg min avg | avg min avg|
> | Scenarios | fps fps pwr | fps fps pwr | fps fps pwr|
> |---------------------------------------------------------------------|
> | HOK game 60fps | 100 100 100 | 105 *134* 102 | 104 *152* 106|
> | HOK game 90fps | 100 100 100 | 101 *114* 101 | 103 *129* 105|
> | HOK game 120fps | 100 100 100 | 102 *124* 102 | 105 *134* 105|
> | FHD video rec. 60fps | 100 100 100 | n/a n/a n/a | 100 100 103|
> | Camera snapshot | 100 100 100 | n/a n/a n/a | 100 100 102|
> -----------------------------------------------------------------------
>
> HOK ... Honour Of Kings, Video game
> FHD ... Full High Definition
> fps ... frame per second
> pwr ... power consumption
>
> table values are in %
I assume that you are specifically interested in those higher min fps
numbers which can be achieved with a tolerable energy consumption
increase when running the game with 16ms or even 8ms PELT halflife.
We see a similar effect when running the UI performance benchmark
Jankbench.
So you need this runtime-switchable PELT multiplier. Would this sched
feature interface:
https://lkml.kernel.org/r/YwyOzgbbUbB+JmSH@hirez.programming.kicks-ass.net
be sufficient for you? People don't like to support `changing PELT
halflife` via an official sysctl.
[...]
next prev parent reply other threads:[~2022-09-28 17:10 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 5:54 [RFC PATCH 0/1] sched/pelt: Change PELT halflife at runtime Dietmar Eggemann
2022-08-29 5:54 ` [RFC PATCH 1/1] sched/pelt: Introduce PELT multiplier Dietmar Eggemann
2022-08-29 8:08 ` Peter Zijlstra
2022-08-29 10:02 ` Peter Zijlstra
2022-08-29 10:13 ` Vincent Guittot
2022-08-29 14:23 ` Quentin Perret
2022-08-29 14:34 ` Peter Zijlstra
2022-08-29 15:31 ` Quentin Perret
2022-08-29 15:48 ` Quentin Perret
2022-09-02 7:53 ` Dietmar Eggemann
2022-09-02 8:45 ` Peter Zijlstra
2022-09-06 5:49 ` Vincent Guittot
2022-09-08 6:50 ` Dietmar Eggemann
2022-09-02 7:53 ` Dietmar Eggemann
2022-09-02 8:45 ` Peter Zijlstra
2022-09-20 14:07 ` [RFC PATCH 0/1] sched/pelt: Change PELT halflife at runtime Jian-Min Liu
2022-09-28 17:09 ` Dietmar Eggemann [this message]
2022-09-29 9:47 ` Peter Zijlstra
2022-09-29 11:07 ` Dietmar Eggemann
2022-09-29 11:10 ` Kajetan Puchalski
2022-09-29 11:21 ` Peter Zijlstra
2022-09-29 14:41 ` Kajetan Puchalski
2022-10-03 22:57 ` Wei Wang
2022-10-04 9:33 ` Dietmar Eggemann
2022-10-05 16:57 ` Wei Wang
2022-11-07 13:41 ` Peter Zijlstra
2022-11-08 19:48 ` Qais Yousef
2022-11-09 15:49 ` Peter Zijlstra
2022-11-10 13:25 ` Qais Yousef
2023-02-07 10:29 ` Dietmar Eggemann
2023-02-09 16:16 ` Vincent Guittot
2023-02-17 13:54 ` Dietmar Eggemann
2023-02-20 13:54 ` Vincent Guittot
2023-02-21 9:29 ` Vincent Guittot
2023-02-22 20:28 ` Dietmar Eggemann
2023-03-01 10:24 ` Vincent Guittot
2023-02-22 20:13 ` Dietmar Eggemann
2023-03-02 19:36 ` Dietmar Eggemann
2023-02-20 10:13 ` Peter Zijlstra
2023-02-20 13:39 ` Vincent Guittot
2023-02-23 15:37 ` Qais Yousef
2023-03-01 10:39 ` Vincent Guittot
2023-03-01 17:24 ` Qais Yousef
2023-03-02 8:00 ` Vincent Guittot
2023-03-02 19:39 ` Dietmar Eggemann
2023-03-06 19:11 ` Qais Yousef
2023-03-07 13:22 ` Vincent Guittot
2023-03-11 16:55 ` Qais Yousef
2023-03-23 16:29 ` Dietmar Eggemann
2023-04-03 14:45 ` Qais Yousef
2023-04-06 15:58 ` Dietmar Eggemann
2023-04-11 17:51 ` Qais Yousef
2022-11-09 15:18 ` Lukasz Luba
2022-11-10 11:16 ` Dietmar Eggemann
2022-11-10 13:05 ` Peter Zijlstra
2022-11-10 14:59 ` Dietmar Eggemann
2022-11-10 17:51 ` Peter Zijlstra
2022-11-30 18:14 ` Dietmar Eggemann
2022-12-01 13:37 ` Kajetan Puchalski
2022-11-10 12:45 ` Kajetan Puchalski
2022-11-07 9:41 ` Jian-Min Liu (劉建旻)
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=ef5fcbf2-e018-9af2-48c3-9fea3109b27f@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=adharmap@quicinc.com \
--cc=jian-min.liu@mediatek.com \
--cc=jonathan.jmchen@mediatek.com \
--cc=kajetan.puchalski@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@matbug.net \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=qperret@google.com \
--cc=vdonnefort@google.com \
--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 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.