cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 65501] Blind angle of 1% between up_threshold and down_threshold
Date: Thu, 19 Dec 2013 01:59:47 +0000	[thread overview]
Message-ID: <bug-65501-12968-fVMOQlZbUm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-65501-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=65501

--- Comment #14 from Viresh Kumar <viresh.kumar@linaro.org> ---
(In reply to sworddragon2 from comment #13)
> This is the point that disturbs me. We are setting a fixed minimum limit of
> 11 while there is no logical reason to do this.

This must be based on the reasoning that we don't have to go to max freq for
loads as low as 10%. That sounds reasonable too, atleast to me. If you want
such system where you want to go to max freq as soon as there is any load then
better use performance governor. Otherwise what's currently in there looks good
to me. I would actually say even 10% is a very low value of min up_threshold.
It could have been more :)

Don't know what Rafael have to say on this.

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

  parent reply	other threads:[~2013-12-19  1:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 14:53 [Bug 65501] New: Blind angle of 1% between up_threshold and down_threshold bugzilla-daemon
2013-11-26 21:43 ` [Bug 65501] " 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 [this message]
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-fVMOQlZbUm@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 NNTP newsgroup(s).