RE: cpu clock change latency

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> this improves latency of the GUI. Note that the comment said "us", while the
> cpu transition latency is measured in "ns", so 400 * 1000 would be right.
> 
> So either the comment is wrong (should be 400ns) or the patch is wrong
> (which is unlikely, because it improved latency in the testcase).
> 

You're right, the patch is wrong.  It should be 400us.  So the original code was much closer to the correct value.

The ondemand governor samples at 1000 times the transition latency, so it's not surprising it works fine with the wrong value at least with ondemand.  The interactive governor in android ignores transition latency.

Perhaps a better fix would be to make the hardcoded LATENCY_MULTIPLIER in the ondemand governor a tunable?

-Allen

--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [ARM Kernel]     [Linux ARM]     [Linux ARM MSM]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux