[gentoo-user] Re: Check CPU for throttling
Alan McKinnon alan.mckinnon at gmail.com writes: otherwise. Just enable ondemand, disable everything else, and et the kernel get on with doing what it does best: So this is what you are saying? [*] CPU Frequency scaling │ │ │ │[*] Enable CPUfreq debugging│ │ │ │* CPU frequency translation statistics│ │ │ │[ ] CPU frequency translation statistics details │ │ │ │ Default CPUFreq governor (performance) ---│ │ │ │-*- 'performance' governor │ │ │ │'powersave' governor│ │ │ │'userspace' governor for userspace frequency scaling│ │ │ │* 'ondemand' cpufreq policy governor │ │ │ │'conservative' cpufreq governor │ │ │ │ *** CPUFreq processor drivers *** │ │ │ │Processor Clocking Control interface driver │ │ │ │* ACPI Processor P-States driver │ │ │ │AMD Opteron/Athlon64 PowerNow! │ │ │ │Intel Enhanced SpeedStep (deprecated) │ │ │ │Intel Pentium 4 clock modulation
Re: [gentoo-user] Re: Check CPU for throttling
On 05/10/2011 09:34 AM, James wrote: Alan McKinnon alan.mckinnon at gmail.com writes: otherwise. Just enable ondemand, disable everything else, and et the kernel get on with doing what it does best: So this is what you are saying? [*] CPU Frequency scaling │ │ │ │[*] Enable CPUfreq debugging│ │ │ │* CPU frequency translation statistics│ │ │ │[ ] CPU frequency translation statistics details │ │ │ │ Default CPUFreq governor (performance) ---│ │ │ │-*- 'performance' governor │ │ │ │'powersave' governor│ │ │ │'userspace' governor for userspace frequency scaling│ │ │ │* 'ondemand' cpufreq policy governor │ │ │ │'conservative' cpufreq governor │ │ │ │ *** CPUFreq processor drivers *** │ │ │ │Processor Clocking Control interface driver │ │ │ │* ACPI Processor P-States driver │ │ │ │AMD Opteron/Athlon64 PowerNow! │ │ │ │Intel Enhanced SpeedStep (deprecated) │ │ │ │Intel Pentium 4 clock modulation Yes but no. Yes, those are the correct choices, but the default governor should be ondemand.
Re: [gentoo-user] Re: Check CPU for throttling
On Tue, May 10, 2011 at 9:38 AM, Bill Longman bill.long...@gmail.com wrote: On 05/10/2011 09:34 AM, James wrote: Alan McKinnon alan.mckinnon at gmail.com writes: otherwise. Just enable ondemand, disable everything else, and et the kernel get on with doing what it does best: So this is what you are saying? [*] CPU Frequency scaling │ │ │ │ [*] Enable CPUfreq debugging │ │ │ │ * CPU frequency translation statistics │ │ │ │ [ ] CPU frequency translation statistics details │ │ │ │ Default CPUFreq governor (performance) --- │ │ │ │ -*- 'performance' governor │ │ │ │ 'powersave' governor │ │ │ │ 'userspace' governor for userspace frequency scaling│ │ │ │ * 'ondemand' cpufreq policy governor │ │ │ │ 'conservative' cpufreq governor │ │ │ │ *** CPUFreq processor drivers *** │ │ │ │ Processor Clocking Control interface driver │ │ │ │ * ACPI Processor P-States driver │ │ │ │ AMD Opteron/Athlon64 PowerNow! │ │ │ │ Intel Enhanced SpeedStep (deprecated) │ │ │ │ Intel Pentium 4 clock modulation Yes but no. Yes, those are the correct choices, but the default governor should be ondemand. Or in the case of the OP who is brave enough (or silly enough?) to risk the long term reliability of his CPU running it with no fan, possibly choose powersave with a specific low clock rate as the default and then switch to either ondemand or conservative manually when he needs more performance. In a machine such as he's playing with I wonder if he really wants ondemand (jumps to max and then slows down over time) vs conservative which more slowly ramps up the clock rate if the job at hand takes more time. It's all a trade off of performance vs power heat. On my 12 thread server I've played with these two and frankly don't see a lot of difference doing any large job. They are both a bot slower than running performance, but I save a lot of power (and over time money) using them so I'm happy. - Mark
Re: [gentoo-user] Re: Check CPU for throttling
Apparently, though unproven, at 18:34 on Tuesday 10 May 2011, James did opine thusly: Alan McKinnon alan.mckinnon at gmail.com writes: otherwise. Just enable ondemand, disable everything else, and et the kernel get on with doing what it does best: So this is what you are saying? [*] CPU Frequency scaling │ │ │ │[*] Enable CPUfreq debugging│ │ │ │* CPU frequency translation statistics│ │ │ │[ ] CPU frequency translation statistics details │ │ │ │ Default CPUFreq governor (performance) ---│ │ │ │-*- 'performance' governor │ │ │ │'powersave' governor│ │ │ │'userspace' governor for userspace frequency scaling│ │ │ │* 'ondemand' cpufreq policy governor │ │ │ │'conservative' cpufreq governor │ │ │ │ *** CPUFreq processor drivers *** │ │ │ │Processor Clocking Control interface driver │ │ │ │* ACPI Processor P-States driver │ │ │ │AMD Opteron/Athlon64 PowerNow! │ │ │ │Intel Enhanced SpeedStep (deprecated) │ │ │ │Intel Pentium 4 clock modulation Mostly. The performance governor cannot be disabled (-*-) so it is always selected, and the default should be set to ondemand. The above is for personal workstations, laptops etc. For servers requiring decent throughput and where power and cooling is not an issue, one would use a different approach of course. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Re: Check CPU for throttling
On Tuesday 10 May 2011 19:05:08 Mark Knecht wrote: On Tue, May 10, 2011 at 9:38 AM, Bill Longman bill.long...@gmail.com wrote: On 05/10/2011 09:34 AM, James wrote: Alan McKinnon alan.mckinnon at gmail.com writes: otherwise. Just enable ondemand, disable everything else, and et the kernel get on with doing what it does best: So this is what you are saying? [*] CPU Frequency scaling │ │ │ │[*] Enable CPUfreq debugging│ │ │ │* CPU frequency translation statistics│ │ │ │[ ] CPU frequency translation statistics details │ │ │ │ Default CPUFreq governor (performance) ---│ │ │ │-*- 'performance' governor │ │ │ │'powersave' governor│ │ │ │'userspace' governor for userspace frequency scaling│ │ │ │* 'ondemand' cpufreq policy governor │ │ │ │'conservative' cpufreq governor │ │ │ │ *** CPUFreq processor drivers *** │ │ │ │Processor Clocking Control interface driver │ │ │ │* ACPI Processor P-States driver │ │ │ │AMD Opteron/Athlon64 PowerNow! │ │ │ │Intel Enhanced SpeedStep (deprecated) │ │ │ │Intel Pentium 4 clock modulation Yes but no. Yes, those are the correct choices, but the default governor should be ondemand. Or in the case of the OP who is brave enough (or silly enough?) to risk the long term reliability of his CPU running it with no fan, possibly choose powersave with a specific low clock rate as the default and then switch to either ondemand or conservative manually when he needs more performance. In a machine such as he's playing with I wonder if he really wants ondemand (jumps to max and then slows down over time) vs conservative which more slowly ramps up the clock rate if the job at hand takes more time. It's all a trade off of performance vs power heat. On my 12 thread server I've played with these two and frankly don't see a lot of difference doing any large job. They are both a bot slower than running performance, but I save a lot of power (and over time money) using them so I'm happy. I just checked on a Pentium 4 32bit box and I couldn't find any declaration about cpufreq under /sys/devices/system/cpu/cpu0/ I have enabled ondemand since I first built a kernel for that machine, but it seems to have been pegged at 3.4GHz even when the plasma thingy shows minimum CPU load. grep MHz /proc/cpuinfo cpu MHz : 3401.054 cpu MHz : 3401.054 ls -la /sys/devices/system/cpu/cpu0/ total 0 drwxr-xr-x 6 root root 0 May 10 18:51 . drwxr-xr-x 6 root root 0 May 10 18:51 .. drwxr-xr-x 4 root root 0 May 10 21:04 cache drwxr-xr-x 2 root root 0 May 10 21:04 microcode drwxr-xr-x 2 root root 0 May 10 21:04 thermal_throttle drwxr-xr-x 2 root root 0 May 10 21:04 topology cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 3 model name : Intel(R) Pentium(R) 4 CPU 3.40GHz stepping: 4 cpu MHz : 3401.054 cache size : 1024 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc pebs bts pni dtes64 monitor ds_cpl cid xtpr bogomips: 6802.10 clflush size: 64 cache_alignment : 128 address sizes : 36 bits physical, 32 bits virtual power management: Same with the other virtual core, power management is blank. Am I missing something in my kernel or is my MoBo/CPU feature poor? cat .config | grep CPU_FREQ CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=y CONFIG_CPU_FREQ_STAT_DETAILS=y # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_GOV_POWERSAVE is not set CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Check CPU for throttling
On 05/10/2011 01:30 PM, Mick wrote: Same with the other virtual core, power management is blank. Am I missing something in my kernel or is my MoBo/CPU feature poor? cat .config | grep CPU_FREQ CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=y CONFIG_CPU_FREQ_STAT_DETAILS=y # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_GOV_POWERSAVE is not set CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set It usually comes down to capabilities in your BIOS, Mick. My P4 won't do it either, but that's on a Dell server from 2004. No BIOS support. And the CPU can do HT but the BIOS is stupid, too. I still have only one CPU/thread.
Re: [gentoo-user] Re: Check CPU for throttling
On Tuesday 10 May 2011 21:36:40 Bill Longman wrote: On 05/10/2011 01:30 PM, Mick wrote: Same with the other virtual core, power management is blank. Am I missing something in my kernel or is my MoBo/CPU feature poor? It usually comes down to capabilities in your BIOS, Mick. My P4 won't do it either, but that's on a Dell server from 2004. No BIOS support. And the CPU can do HT but the BIOS is stupid, too. I still have only one CPU/thread. Thanks Bill, I seem to recall something about Stepping in the BIOS settings (can't reboot at the moment without risking a domestic incident ...) and I think I have it enabled (or auto?) If it is there and I'm not imagining things I'll try disabling it perhaps and see if the kernel can take over. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
