All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 69821] setting CONFIG_HZ_PERIODIC locks cpu at the lowest frequency using ONDEMAND
Date: Tue, 11 Feb 2014 10:01:18 +0000	[thread overview]
Message-ID: <bug-69821-12968-3bTshnn9k4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-69821-12968@https.bugzilla.kernel.org/>

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

--- Comment #2 from j.fikar@gmail.com ---
Well, I was trying the new CONFIG_NO_HZ_FULL and comparing it to the two old
CONFIG_NO_HZ_IDLE and CONFIG_HZ_PERIODIC. To my surprise the oldest (and I
thought most stable and most tested) CONFIG_HZ_PERIODIC causes problems with
CPU scaling.

On the other hand, I'm aware that CONFIG_NO_HZ_IDLE is the recommended default
and that there was a lot of recent development due to the new
CONFIG_NO_HZ_FULL. 

Anyway, I think it is a bug and not expected behaviour, right?

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

  parent reply	other threads:[~2014-02-11 10:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-69821-12968@https.bugzilla.kernel.org/>
2014-02-07  2:40 ` [Bug 69821] setting CONFIG_HZ_PERIODIC locks cpu at the lowest frequency using ONDEMAND bugzilla-daemon
2014-02-11  0:52 ` bugzilla-daemon
2014-02-11 10:01 ` bugzilla-daemon [this message]
2014-06-03  6:14 ` bugzilla-daemon
2015-12-15  0:12 ` bugzilla-daemon
2015-12-16  2:09 ` bugzilla-daemon
2015-12-16  2:15 ` bugzilla-daemon
2015-12-16  2:43 ` 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-69821-12968-3bTshnn9k4@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 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.