public inbox for cpufreq@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 55261] down_threshold is missing
Date: Fri, 15 Mar 2013 12:02:09 +0000 (UTC)	[thread overview]
Message-ID: <20130315120209.86C2611F8CD@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-55261-12968@https.bugzilla.kernel.org/>

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





--- Comment #2 from sworddragon2@aol.com  2013-03-15 12:02:09 ---
This makes it dificult to get an early upscaling of the cpu frequency. I'm
trying to achieve this at ~1% cpu usage. Would it be possible after this commit
to allow up_threshold to be lower (for example 1 on my system)?

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2013-03-15 12:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15  6:14 [Bug 55261] New: down_threshold is missing bugzilla-daemon
2013-03-15  8:58 ` [Bug 55261] " bugzilla-daemon
2013-03-15 12:02 ` bugzilla-daemon [this message]
2013-03-26  7:47 ` bugzilla-daemon
2013-03-26  7:47 ` bugzilla-daemon
2013-04-18  6:59 ` 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=20130315120209.86C2611F8CD@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