On 03/03/16 17:56, Peter Zijlstra wrote: > On Thu, Mar 03, 2016 at 04:55:44PM +0000, Juri Lelli wrote: > > On 03/03/16 17:37, Peter Zijlstra wrote: > > > But given the platform's cpuidle information, maybe coupled with an avg > > > idle est, we can compute the benefit of race-to-idle and over provision > > > based on that, right? > > > > > > > Shouldn't this kind of considerations be a scheduler thing? I'm not > > really getting why we want to put more "intelligence" in a new governor. > > Also, if I understand Ingo's point correctly, I think we want to make > > this kind of policy decisions inside the scheduler. > > Well sure, put it in kernel/sched/cpufreq.c or wherever. My point was > more that we don't have to guess/hardcode race-to-idle assumptions but > can actually calculate some of that. > Right, thanks for clarifying! -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
