From: Alexander Clouter <alex@digriz.org.uk>
To: cpufreq@lists.linux.org.uk
Cc: davej@redhat.com, linux@dominikbrodowski.de, alex-kernel@digriz.org.uk
Subject: [PATCH] (3/3) cpufreq_ondemand - 03_sys_freq_step.diff
Date: Tue, 10 May 2005 23:32:17 +0100 [thread overview]
Message-ID: <20050510223217.GD4478@inskipp> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 490 bytes --]
Adds support so that the cpufreq change stepping is no longer fixed at 5% and
can be changed dynamically by the user
Signed-off-by: Alexander Clouter <alex-kernel@digriz.org.uk>
--
_______________________________________
/ It is a poor judge who cannot award a \
\ prize. /
---------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
[-- Attachment #1.1.2: cpufreq_ondemand-2.6.12-rc3-mm3-03_sys_freq_step.diff --]
[-- Type: text/plain, Size: 3044 bytes --]
--- linux-2.6.12-rc3-mm3.orig/drivers/cpufreq/cpufreq_ondemand.c 2005-05-10 22:23:51.692480816 +0100
+++ linux-2.6.12-rc3-mm3/drivers/cpufreq/cpufreq_ondemand.c 2005-05-10 22:24:10.032692680 +0100
@@ -79,6 +79,7 @@
unsigned int up_threshold;
unsigned int down_threshold;
unsigned int ignore_nice;
+ unsigned int freq_step;
};
static struct dbs_tuners dbs_tuners_ins = {
@@ -117,6 +118,7 @@
show_one(up_threshold, up_threshold);
show_one(down_threshold, down_threshold);
show_one(ignore_nice, ignore_nice);
+show_one(freq_step, freq_step);
static ssize_t store_sampling_down_factor(struct cpufreq_policy *unused,
const char *buf, size_t count)
@@ -235,6 +237,29 @@
return count;
}
+static ssize_t store_freq_step(struct cpufreq_policy *policy,
+ const char *buf, size_t count)
+{
+ unsigned int input;
+ int ret;
+
+ ret = sscanf (buf, "%u", &input);
+
+ if ( ret != 1 )
+ return -EINVAL;
+
+ if ( input > 100 )
+ input = 100;
+
+ /* no need to test here if freq_step is zero as the user might actually
+ * want this, they would be crazy though :) */
+ down(&dbs_sem);
+ dbs_tuners_ins.freq_step = input;
+ up(&dbs_sem);
+
+ return count;
+}
+
#define define_one_rw(_name) \
static struct freq_attr _name = \
__ATTR(_name, 0644, show_##_name, store_##_name)
@@ -244,6 +269,7 @@
define_one_rw(up_threshold);
define_one_rw(down_threshold);
define_one_rw(ignore_nice);
+define_one_rw(freq_step);
static struct attribute * dbs_attributes[] = {
&sampling_rate_max.attr,
@@ -253,6 +279,7 @@
&up_threshold.attr,
&down_threshold.attr,
&ignore_nice.attr,
+ &freq_step.attr,
NULL
};
@@ -291,7 +318,7 @@
*
* Any frequency increase takes it to the maximum frequency.
* Frequency reduction happens at minimum steps of
- * 5% of max_frequency
+ * 5% (default) of max_frequency
*/
/* Check for frequency increase */
@@ -390,18 +417,20 @@
usecs_to_jiffies(freq_down_sampling_rate);
if (idle_ticks > down_idle_ticks ) {
- /* if we are already at the lowest speed then break out early */
- if (policy->cur == policy->min)
+ /* if we are already at the lowest speed then break out early
+ * or if we 'cannot' reduce the speed as the user might want
+ * freq_step to be zero */
+ if (policy->cur == policy->min || dbs_tuners_ins.freq_step == 0)
return;
-
- freq_down_step = (5 * policy->max) / 100;
+
+ freq_down_step = (dbs_tuners_ins.freq_step * policy->max) / 100;
/* max freq cannot be less than 100. But who knows.... */
if (unlikely(freq_down_step == 0))
freq_down_step = 5;
__cpufreq_driver_target(policy,
- policy->cur - freq_down_step,
+ policy->cur - freq_down_step,
CPUFREQ_RELATION_H);
return;
}
@@ -486,6 +515,7 @@
DEF_SAMPLING_RATE_LATENCY_MULTIPLIER;
dbs_tuners_ins.sampling_rate = def_sampling_rate;
dbs_tuners_ins.ignore_nice = 0;
+ dbs_tuners_ins.freq_step = 5;
dbs_timer_init();
}
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 147 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq
next reply other threads:[~2005-05-10 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 22:32 Alexander Clouter [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-20 13:18 [PATCH] (3/3) cpufreq_ondemand - 03_sys_freq_step.diff Alexander Clouter
2005-02-21 15:17 ` Bruno Ducrot
2005-02-21 15:26 ` Dominik Brodowski
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=20050510223217.GD4478@inskipp \
--to=alex@digriz.org.uk \
--cc=alex-kernel@digriz.org.uk \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=linux@dominikbrodowski.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox