Messages in this thread | | | Date | Tue, 21 Oct 2003 22:37:36 +0200 | From | Dominik Brodowski <> | Subject | Re: [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI P-state driver |
| |
On Tue, Oct 21, 2003 at 12:23:18PM -0700, Carl Thompson wrote: > > In other words: there is no valid way that a _user_ can set the policy > > right now: the user can set the frequency, but since any sane policy > > depends on how busy the CPU is, the user isn't even, the right person to > > _do_ that, since the user doesn't _know_. > > But userspace _can_ know the idle statistics for each CPU. It's easily read > from /proc/stat.
Well, /proc/stat, and kstat_cpu is very inaccurate. There's a project going on to get better statistics for usage by cpufreq governors. And you really don't want to export all sorts of statistics every, or every tenth timer tick to userspace. But if it's done in kernel-space, and if it's done right, it may cost really few percentage points of performance.
Even though the governor proposed by Venkatesh may be done as well in userspace [which I doubt], it's only one of several possible dynamic cpufreq governors, most of which will be much faster, leaner and meaner in kernel space.
Dominik - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |