All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 30712] Slow transitioning AMD ondemand CPU because of wrong sampling_rate
Date: Tue, 29 Mar 2011 15:29:12 GMT	[thread overview]
Message-ID: <201103291529.p2TFTCfD030280@demeter1.kernel.org> (raw)
In-Reply-To: <bug-30712-12968@https.bugzilla.kernel.org/>

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


Thomas Renninger <trenn@suse.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |ASSIGNED
         AssignedTo|cpufreq@vger.kernel.org     |trenn@suse.de




--- Comment #7 from Thomas Renninger <trenn@suse.de>  2011-03-29 15:29:11 ---
> Decreasing sampling_rate is still good for performance, but the total time is
> much shorter in every cases
Thanks, so there may be a fix/improvement in 2.6.38?

It will still take some time, as this is rather time intensive.
Also prio is not that high as there is no real regression.
But I am going to revisit the issue in some weeks and may come up with some
fine tuning.

-- 
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:[~2011-03-29 15:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 21:54 [Bug 30712] New: Slow transitioning AMD ondemand CPU because of wrong sampling_rate bugzilla-daemon
2011-03-07 21:54 ` [Bug 30712] " bugzilla-daemon
2011-03-08  9:17 ` bugzilla-daemon
2011-03-15  4:59 ` bugzilla-daemon
2011-03-24 17:30 ` bugzilla-daemon
2011-03-24 21:58 ` bugzilla-daemon
2011-03-28  1:47 ` bugzilla-daemon
2011-03-28  5:28 ` bugzilla-daemon
2011-03-29 15:29 ` bugzilla-daemon [this message]

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=201103291529.p2TFTCfD030280@demeter1.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.