I use the following one liner for regression tests of the cpufreq governor and friends:
[EMAIL PROTECTED] ~ $ time factor 819734028463158891 which usually needs 5.5 secs to complete at 1.7 GHz of my pentium M processor. With the current git sources (commit cfa76f0 at Sat Oct 20 20:19:15 2007 -0700) instead this command needs 3 times longer if I run the "distributed.net client" as a background process with nice level 19 b/c the cpu frequency still stays at 600 MHz. After stopping dnetc the cpu frequency governor ondemand works as expected again. Tested at my ThinkPad T41 with stable Gentoo: [EMAIL PROTECTED] ~ $ grep -e ^CONFIG_ACPI -e ^CONFIG_CPU_FREQ_GOV_ ~/devel/linux-2.6/.config CONFIG_ACPI=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_PROCFS=y CONFIG_ACPI_PROC_EVENT=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=m CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_THERMAL=m CONFIG_ACPI_BLACKLIST_YEAR=0 CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_SYSTEM=y CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_ONDEMAND=y -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
