From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 54761] Variable cpu frequency causes to loose performance
Date: Tue, 26 Mar 2013 09:41:40 +0000 (UTC) [thread overview]
Message-ID: <20130326094140.C5A3211FB0C@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-54761-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=54761
--- Comment #4 from Viresh Kumar <viresh.kumar@linaro.org> 2013-03-26 09:41:40 ---
1400 MHz would always be slower than 2700 MHz. And ondemand can't simply switch
to max without much load. So, you can say it that way "Ondemand sometimes have
performance impact" :)
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2013-03-26 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 14:01 [Bug 54761] New: Variable cpu frequency causes to loose performance bugzilla-daemon
2013-03-26 7:43 ` [Bug 54761] " bugzilla-daemon
2013-03-26 9:08 ` bugzilla-daemon
2013-03-26 9:15 ` bugzilla-daemon
2013-03-26 9:41 ` bugzilla-daemon [this message]
2013-03-26 13:24 ` bugzilla-daemon
2013-04-18 9:12 ` 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=20130326094140.C5A3211FB0C@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