On 12/14/2015 06:22 PM, Yuyang Du wrote: > what if we just init the util_avg to 0?
With scheduler-guided frequency [1] we will rely on the initial util_avg value to determine the CPU frequency response when new tasks are created. There is sure to be a lot of debate on what sort of default policy is used (and how much that can be changed with tunables). IMO at least for now, new tasks should cause the target CPU to go to fmax, especially given how slow PELT is to respond to changes in task behavior. This would imply leaving the initial task util_avg at 100% (or the equivalent necessary to take care of the overflow issues). [1] https://lkml.org/lkml/2015/12/9/35 thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
