From: Eric Piel <Eric.Piel@tremplin-utc.net>
To: Alex Simonov <a_simonov@yahoo.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Ondemand governor not working with kernel-2.6.12-12mdk
Date: Mon, 10 Oct 2005 23:24:56 +0200 [thread overview]
Message-ID: <434ADC28.5020707@tremplin-utc.net> (raw)
In-Reply-To: <20051008173032.52611.qmail@web32704.mail.mud.yahoo.com>
08.10.2005 19:30, Alex Simonov wrote/a écrit:
> Hello Eric,
:
>
> Your patch did the trick, thanks! The only draw
> back is that the responsiveness is not
> so good - it takes at least 2-3 seconds to
> switch to the highest frequency and back, when
> thie high load is over. Is it supposed to be like
> that by design, or this latency could be changed?
>
>
That's strange, it's supposed to be faster (although it could be even
faster). IIRC, on 2.6.12, it should be every 100 milliseconds. You can
check the sampling frequency of the ondemand governor by doing a
cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
It will give the period between each frequency update in microseconds.
In general, it should change from low to high in a tenth of a second.
You can check it with a stupid shell command like this (when nothing
else is running), this is only one line:
# date +%T.%N; while test $(cat
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq) != $(cat
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq) ; do true ; done
; date +%T.%N
By doing the difference between the two times displayed you'll know how
long it takes for the ondemand governor to change to the high frequency.
Here (pentium III), it takes about 0.08s .
Eric
next prev parent reply other threads:[~2005-10-10 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43455149.1090702@tremplin-utc.net>
2005-10-08 17:30 ` Ondemand governor not working with kernel-2.6.12-12mdk Alex Simonov
2005-10-10 21:24 ` Eric Piel [this message]
2005-10-06 12:52 Alex Simonov
2005-10-06 14:58 ` Eric Piel
2005-10-06 18:13 ` Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=434ADC28.5020707@tremplin-utc.net \
--to=eric.piel@tremplin-utc.net \
--cc=a_simonov@yahoo.com \
--cc=cpufreq@lists.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.