On 05/12/2015 10:13 AM, Michael Turquette wrote: > This governor is event-driven. There is no polling loop to check cpu > idle time nor any other method which is unsynchronized with the > scheduler. The entry points for this policy are in fair.c: > enqueue_task_fair, dequeue_task_fair and task_tick_fair. > > This policy is implemented using the cpufreq governor interface for two > main reasons: > > 1) re-using the cpufreq machine drivers without using the governor > interface is hard. > > 2) using the cpufreq interface allows us to switch between the > scheduler-driven policy and legacy cpufreq governors such as ondemand at > run-time. This is very useful for comparative testing and tuning.
Hi, Mike, Did you have some testing data with your patch? -- 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/