From: Thara Gopinath <thara.gopinath@linaro.org>
To: Ionela Voinescu <ionela.voinescu@arm.com>,
mingo@redhat.com, peterz@infradead.org, rui.zhang@intel.com
Cc: linux-kernel@vger.kernel.org, amit.kachhap@gmail.com,
viresh.kumar@linaro.org, javi.merino@kernel.org,
edubezval@gmail.com, daniel.lezcano@linaro.org,
vincent.guittot@linaro.org, nicolas.dechesne@linaro.org,
bjorn.andersson@linaro.org, dietmar.eggemann@arm.com
Subject: Re: [PATCH V2 0/3] Introduce Thermal Pressure
Date: Tue, 30 Apr 2019 11:57:54 -0400 [thread overview]
Message-ID: <5CC87082.20802@linaro.org> (raw)
In-Reply-To: <8eed9601-8bbb-9f62-f786-f08bd4a72907@arm.com>
On 04/29/2019 09:29 AM, Ionela Voinescu wrote:
> Hi Thara,
>
>>
>> Hackbench: (1 group , 30000 loops, 10 runs)
>> Result Standard Deviation
>> (Time Secs) (% of mean)
>>
>> No Thermal Pressure 10.21 7.99%
>>
>> Instantaneous thermal pressure 10.16 5.36%
>>
>> Thermal Pressure Averaging
>> using PELT fmwk 9.88 3.94%
>>
>> Thermal Pressure Averaging
>> non-PELT Algo. Decay : 500 ms 9.94 4.59%
>>
>> Thermal Pressure Averaging
>> non-PELT Algo. Decay : 250 ms 7.52 5.42%
>>
>> Thermal Pressure Averaging
>> non-PELT Algo. Decay : 125 ms 9.87 3.94%
>>
>>
>
> I'm trying your patches on my Hikey960 and I'm getting different results
> than the ones here.
>
> I'm running with the step-wise governor, enabled only on the big cores.
> The decay period is set to 250ms.
>
> The result for hackbench is:
>
> # ./hackbench -g 1 -l 30000
> Running in process mode with 1 groups using 40 file descriptors each (== 40 tasks)
> Each sender will pass 30000 messages of 100 bytes
> Time: 20.756
>
> During the run I see the little cores running at maximum frequency
> (1.84GHz) while the big cores run mostly at 1.8GHz, only sometimes capped
> at 1.42GHz. There should not be any capacity inversion.
> The temperature is kept around 75 degrees (73 to 77 degrees).
>
> I don't have any kind of active cooling (no fans on the board), only a
> heatsink on the SoC.
>
> But as you see my results(~20s) are very far from the 7-10s in your
> results.
>
> Do you see anything wrong with this process? Can you give me more
> details on your setup that I can use to test on my board?
Hi Ionela,
I used the latest mainline kernel with sched/ tip merged in for my
testing. My hikey960 did not have any fan or heat sink during testing. I
disabled cpu cooling for little cores in the dts files.
Also I have to warn you that I have managed to blow up my hikey960. So I
no longer have a functional board for past two weeks or so.
I don't have my test scripts to send you, but I have some of the results
files downloaded which I can send you in a separate email.
I did run the test 10 rounds.
Also I think 20s is too much of variation for the test results. Like I
mentioned in my previous emails I think the 7.52 is an anomaly but the
results should be around the range of 8-9 s.
Regards
Thara
>
> Thank you,
> Ionela.
>
--
Regards
Thara
next prev parent reply other threads:[~2019-04-30 15:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 19:38 [PATCH V2 0/3] Introduce Thermal Pressure Thara Gopinath
2019-04-16 19:38 ` [PATCH V2 1/3] Calculate " Thara Gopinath
2019-04-18 10:14 ` Quentin Perret
2019-04-24 4:13 ` Thara Gopinath
2019-04-24 16:38 ` Peter Zijlstra
2019-04-24 16:45 ` Peter Zijlstra
2019-04-25 10:57 ` Quentin Perret
2019-04-25 12:45 ` Vincent Guittot
2019-04-25 12:47 ` Quentin Perret
2019-04-26 14:17 ` Thara Gopinath
2019-05-08 12:41 ` Quentin Perret
2019-04-16 19:38 ` [PATCH V2 2/3] sched/fair: update cpu_capcity to reflect thermal pressure Thara Gopinath
2019-04-16 19:38 ` [PATCH V3 3/3] thermal/cpu-cooling: Update thermal pressure in case of a maximum frequency capping Thara Gopinath
2019-04-18 9:48 ` Quentin Perret
2019-04-23 22:38 ` Thara Gopinath
2019-04-24 15:56 ` Ionela Voinescu
2019-04-26 10:24 ` Thara Gopinath
2019-04-25 10:45 ` Quentin Perret
2019-04-25 12:04 ` Vincent Guittot
2019-04-25 12:50 ` Quentin Perret
2019-04-26 13:47 ` Thara Gopinath
2019-04-24 16:47 ` Peter Zijlstra
2019-04-17 5:36 ` [PATCH V2 0/3] Introduce Thermal Pressure Ingo Molnar
2019-04-17 5:55 ` Ingo Molnar
2019-04-17 17:28 ` Thara Gopinath
2019-04-17 17:18 ` Thara Gopinath
2019-04-17 18:29 ` Ingo Molnar
2019-04-18 0:07 ` Thara Gopinath
2019-04-18 9:22 ` Quentin Perret
2019-04-24 16:34 ` Peter Zijlstra
2019-04-25 17:33 ` Ingo Molnar
2019-04-25 17:44 ` Ingo Molnar
2019-04-26 7:08 ` Vincent Guittot
2019-04-26 8:35 ` Ingo Molnar
2019-04-24 15:57 ` Ionela Voinescu
2019-04-26 11:50 ` Thara Gopinath
2019-04-26 14:46 ` Ionela Voinescu
2019-04-29 13:29 ` Ionela Voinescu
2019-04-30 14:39 ` Ionela Voinescu
2019-04-30 16:10 ` Thara Gopinath
2019-05-02 10:44 ` Ionela Voinescu
2019-04-30 15:57 ` Thara Gopinath [this message]
2019-04-30 16:02 ` Thara Gopinath
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=5CC87082.20802@linaro.org \
--to=thara.gopinath@linaro.org \
--cc=amit.kachhap@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=edubezval@gmail.com \
--cc=ionela.voinescu@arm.com \
--cc=javi.merino@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nicolas.dechesne@linaro.org \
--cc=peterz@infradead.org \
--cc=rui.zhang@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 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).