linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Lukasz Luba <lukasz.luba@arm.com>,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Cc: amitk@kernel.org, Dietmar.Eggemann@arm.com
Subject: Re: [PATCH 1/2] thermal: power allocator: change the 'k_i' coefficient estimation
Date: Tue, 13 Oct 2020 17:56:36 +0200	[thread overview]
Message-ID: <4eab17d6-4232-3b8b-b096-835b13e889c1@linaro.org> (raw)
In-Reply-To: <42360f0f-5d53-085b-536f-33df93b787ca@arm.com>

On 13/10/2020 14:04, Lukasz Luba wrote:
> 
> 
> On 10/13/20 12:22 PM, Daniel Lezcano wrote:
>> On 13/10/2020 12:59, Lukasz Luba wrote:
>>> Hi Daniel,
>>>
>>> On 10/13/20 11:21 AM, Daniel Lezcano wrote:
>>>>
>>>> Hi Lukasz,
>>>>
>>>> On 02/10/2020 14:24, Lukasz Luba wrote:
>>>>> Intelligent Power Allocation (IPA) is built around the PID controller
>>>>> concept. The initialization code tries to setup the environment
>>>>> based on
>>>>> the information available in DT or estimate the value based on minimum
>>>>> power reported by each of the cooling device. The estimation will
>>>>> have an
>>>>> impact on the PID controller behaviour via the related 'k_po', 'k_pu',
>>>>> 'k_i' coefficients and also on the power budget calculation.
>>>>>
>>>>> This change prevents the situation when 'k_i' is relatively big
>>>>> compared
>>>>> to 'k_po' and 'k_pu' values. This might happen when the estimation for
>>>>> 'sustainable_power' returned small value, thus 'k_po' and 'k_pu' are
>>>>> small.
>>>>>
>>>>> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
>>>>> ---

[ ... ]

>>> Yes, I strongly believe that vendor engineers will make experiments with
>>> these values and not go with default. Then they will store the k_pu,
>>> k_po, k_i via sysfs interface, with also sustainable_power.
>>
>> IMHO it is the opposite. For what I've seen, the IPA is not used or the
>> k_* are misunderstood, thus not changed. The PID regulation loop
>> technique is not quite used and known by everyone.
> 
> There is quite a few DT entries of 'sustainable-power' so I assumed
> it is known, but you might be right.

Yes, and if you do not count the Linaro contributions, there are even
less entries.

That may imply the sustainable power is estimated in most of the case if
the vendors are specifying the ipa governor. This series may change the
default behavior, but I guess this is not a problem without the right
k_* in any case.

>>> But I have to also fix the hard-coded k_i in the estimation. As
>>> described above, when we have small power values from abstract scale,
>>> the k_i stays too big.
>>
>> May be it is preferable to adjust the k_* dynamically given the
>> undershot and overshot results? And then add a set of less opaque
>> parameters for the user, like the time or watts, no?
>>
> 
> Hmmmm, this is interesting, I haven't thought about it. Thank you
> for this idea.
> That would require a re-design of current IPA. IPA trying to figure
> out better k_* values... I will discuss it internally.

[ ... ]

> It would take time, definitely more than the proposed small fix
> addressing abstract scale and hard-coded 'k_i'.
> Do you think that this fix can be applied and then I can experiment
> on what you suggested?

Yes, sure. Let me review the patch 2/2.

Thanks

  -- Daniel



-- 
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  reply	other threads:[~2020-10-13 15:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 12:24 [PATCH 0/2] Improve the estimations in Intelligent Power Allocation Lukasz Luba
2020-10-02 12:24 ` [PATCH 1/2] thermal: power allocator: change the 'k_i' coefficient estimation Lukasz Luba
2020-10-13 10:21   ` Daniel Lezcano
2020-10-13 10:59     ` Lukasz Luba
2020-10-13 11:22       ` Daniel Lezcano
2020-10-13 12:04         ` Lukasz Luba
2020-10-13 15:56           ` Daniel Lezcano [this message]
2020-10-02 12:24 ` [PATCH 2/2] thermal: power allocator: estimate sustainable power only once Lukasz Luba
2020-10-08 10:14   ` Ionela Voinescu
2020-10-08 12:34     ` Lukasz Luba

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=4eab17d6-4232-3b8b-b096-835b13e889c1@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=Dietmar.Eggemann@arm.com \
    --cc=amitk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    /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).