RE: [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI P-state driver

From: Nakajima, Jun
Date: Thu Oct 23 2003 - 16:51:39 EST


Me too, because it would be consistent with the other ones; i.e. how the
user perceives them.

Jun
> -----Original Message-----
> From: linux-kernel-owner@xxxxxxxxxxxxxxx [mailto:linux-kernel-
> owner@xxxxxxxxxxxxxxx] On Behalf Of Moore, Robert
> Sent: Thursday, October 23, 2003 1:48 PM
> To: Pavel Machek; Pallipadi, Venkatesh
> Cc: cpufreq@xxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx;
linux-acpi;
> Nakajima, Jun; Mallick, Asit K; Dominik Brodowski
> Subject: RE: [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI
P-
> state driver
>
>
> I would vote for "cpufreq_dynamic"
>
> Bob
>
>
> -----Original Message-----
> From: Pavel Machek [mailto:pavel@xxxxxx]
> Sent: Thursday, October 23, 2003 7:17 AM
> To: Pallipadi, Venkatesh
> Cc: cpufreq@xxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx;
linux-acpi;
> Nakajima, Jun; Mallick, Asit K; Dominik Brodowski
> Subject: Re: [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI
> P-state driver
>
> Hi!
>
> > Patch 3/3: New dynamic cpufreq driver (called
> > DemandBasedSwitch driver), which periodically monitors CPU
> > usage and changes the CPU frequency based on the demand.
> >
> > diffstat dbs3.patch
> > drivers/cpufreq/Kconfig | 25 ++++
> > drivers/cpufreq/Makefile | 1
> > drivers/cpufreq/cpufreq_dbs.c | 214
> >
> Could you name it cpufreq_demand? We have enough
> TLAs as is.
> Pavwl
>
>
> --
> Pavel
> Written on sharp zaurus, because my Velo1 broke. If you have Velo you
> don't need...
>
> -
> To unsubscribe from this list: send the line "unsubscribe
linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/