Hi Daniel,
On Tue, May 08 2018 at 20:04 -0600, Daniel Lezcano wrote:
On Mon, May 07, 2018 at 11:54:08AM -0600, Lina Iyer wrote:
From: Ram Chandrasekar <rkumb...@codeaurora.org>
From: Ram Chandrasekar <rkumb...@codeaurora.org>
Step wise governor increases the mitigation level when the temperature
goes above a threshold and will decrease the mitigation when the
temperature falls below the threshold. If it were a case, where the
temperature hovers around a threshold, the mitigation will be applied
and removed at every iteration. This reaction to the temperature is
inefficient for performance.
The use of hysteresis temperature could avoid this ping-pong of
mitigation by relaxing the mitigation to happen only when the
temperature goes below this lower hysteresis value.
I don't disagree with this but the ping-pong around a temperature is usually
avoided with a P-I-D computation which is implemented with the IPA governor.
Wouldn't be more interesting to add the power numbers like some other
platforms, so the IPA could be used?
Possibly. But we have had better thermal performance for our hardware, with
stepwise and custom governor. Much of the mitigation happens through the
firmware and hardware. The stepwise governor works well for us.
You will probably have better results with the IPA than changing the step-wise
governor behavior (which may potentially impact other users).
This should not impact others who have not implemented the
->get_trip_hyst method.
Thanks,
Lina