All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bug 8081] New: Conservative governor sets wrong and too high sampling rates
@ 2007-02-25 16:28 bugme-daemon
  2007-02-25 20:23 ` Rafał Bilski
  0 siblings, 1 reply; 2+ messages in thread
From: bugme-daemon @ 2007-02-25 16:28 UTC (permalink / raw)
  To: cpufreq

http://bugzilla.kernel.org/show_bug.cgi?id=8081

           Summary: Conservative governor sets wrong and too high sampling
                    rates
    Kernel Version: 2.6.18
            Status: NEW
          Severity: normal
             Owner: cpufreq@www.linux.org.uk
         Submitter: ferriste@libero.it


Most recent kernel where this bug did *NOT* occur: none, all kernels >=2.6.13 
are affected (this governor was added in 2.6.13 if I well remember...)

Distribution: Slackware 11.0

Hardware Environment: Asus laptop with amd athlon xp-m 2800+
Software Environment:

Problem Description: When conservative governor is selected, the minimun and 
maximum sampling rate are set to a value 10 times higher than normal, and the 
governor looks at system load only 1 times per second approximately. On my 
laptop, the ondemand governor has a minimum sampling rate of 99500 (0.0995 
seconds) while with conservative this value is 995000 (0.995 seconds). If one 
considers that the default sampling rate is set to 2*minimum, most of users 
will find the conservative governor useless if they don't know how to modify 
it, because the system will not respond to a rapid increasing load.

The reason of this bug is a wrong defined value in the source file of 
conservative. If you look at conservative.c at line 497, you will find this:

def_sampling_rate = 10 * latency * 					
DEF_SAMPLING_RATE_LATENCY_MULTIPLIER;

this should be changed to:

def_sampling_rate = latency * 					
DEF_SAMPLING_RATE_LATENCY_MULTIPLIER;

as is in the ondemand governor. I've recompiled the module with this change 
and now conservative works fine.

My values
Conservative governor (2.6.18 kernel from kernel.org): a cat in the 
conservative folder shows:

bash-3.1# cat sampling_rate_min sampling_rate_max
995000
995000000

Patched conservative (with the correction indicated above):

bash-3.1# cat sampling_rate_min sampling_rate_max
99500
99500000

Ondemand governor (2.6.18 kernel from kernel.org):
bash-3.1# cat sampling_rate_min sampling_rate_max
99500
99500000


Steps to reproduce: cd /sys/devices/system/cpu/cpu0/cpufreq/
echo ondemand > scaling_governor
than take a look in the ondemand folder at files sampling_rate_min, 
sampling_rate_max, sampling rate.
Than do the same thing with conservative:
echo conservative > scaling_governor
and compare the values. You will see that these values are from 10 times (most 
recents kernels) to 100 times (kernels 2.6.13 from 2.6.15) higher than 
ondemand sets.

You can also load the cpufreq_stats module and look in the stats folder 
(/sys/.../cpufreq/stats). You will see that ondemand causes a lot of 
transitions, while conservative does not.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-02-25 20:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-02-25 16:28 [Bug 8081] New: Conservative governor sets wrong and too high sampling rates bugme-daemon
2007-02-25 20:23 ` Rafał Bilski

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.