From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 65501] New: Blind angle of 1% between up_threshold and down_threshold
Date: Fri, 22 Nov 2013 14:53:19 +0000 [thread overview]
Message-ID: <bug-65501-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=65501
Bug ID: 65501
Summary: Blind angle of 1% between up_threshold and
down_threshold
Product: Power Management
Version: 2.5
Kernel Version: Ubuntu 3.12.0-3.9-generic 3.12.1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: cpufreq@vger.kernel.org
Reporter: sworddragon2@aol.com
Regression: No
The lowest value that /sys/devices/system/cpu/cpufreq/ondemand/up_threshold can
contain is 11 while the implicit configuration down_threshold will be
statically set to 10. But I'm thinking that it would be correct if up_threshold
could be set to 10 too as this wouldn't cause any collision. up_threshold would
scale if the cpu core reaches 10% or more of cpu usage (>=) and down_threshold
would scale if the cpu core reaches less than 10% of cpu usage (<).
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2013-11-22 14:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 14:53 bugzilla-daemon [this message]
2013-11-26 21:43 ` [Bug 65501] Blind angle of 1% between up_threshold and down_threshold bugzilla-daemon
2013-12-11 8:59 ` bugzilla-daemon
2013-12-18 6:16 ` bugzilla-daemon
2013-12-18 10:52 ` bugzilla-daemon
2013-12-18 10:56 ` bugzilla-daemon
2013-12-18 11:02 ` bugzilla-daemon
2013-12-18 11:09 ` bugzilla-daemon
2013-12-18 12:14 ` bugzilla-daemon
2013-12-18 14:29 ` bugzilla-daemon
2013-12-18 14:33 ` bugzilla-daemon
2013-12-18 14:42 ` bugzilla-daemon
2013-12-18 14:53 ` bugzilla-daemon
2013-12-18 15:16 ` bugzilla-daemon
2013-12-18 15:29 ` bugzilla-daemon
2013-12-19 1:59 ` bugzilla-daemon
2013-12-19 10:10 ` bugzilla-daemon
2013-12-19 10:16 ` bugzilla-daemon
2014-04-18 3:01 ` bugzilla-daemon
2014-06-03 5:52 ` bugzilla-daemon
2015-11-10 22:49 ` bugzilla-daemon
2015-12-24 13:04 ` bugzilla-daemon
2015-12-24 23:53 ` bugzilla-daemon
2015-12-28 2:44 ` bugzilla-daemon
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=bug-65501-12968@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).