From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: Melanie Kambadur <melanie@cs.columbia.edu>,
Viresh Kumar <viresh.kumar@linaro.org>,
David C Niemi <dniemi@verisign.com>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: powersave governor runs programs faster and uses more power than performance governor
Date: Fri, 25 Oct 2013 07:40:12 -0700 [thread overview]
Message-ID: <526A82CC.1040709@gmail.com> (raw)
In-Reply-To: <CAMeUXYuQobSo7Au07V2KBE6=mAqXW1Hj--G92FP0X1H97Kv8OA@mail.gmail.com>
On 10/24/2013 12:42 PM, Melanie Kambadur wrote:
>
> From /sys/devices/system/cpu/cpuN/cpufreq/scaling_driver I get that
> the current p-state driver is called "intel_pstate". David, you
> mention that the firmware governors are not very efficient, do you
> suggest replacing the intel_pstate driver with a different driver?
I will need to look and see why changing to performance isn't working
correctly.
To get the behavior of the performance governor you can use
echo 100 > /sys/devices/system/cpu/intel_pstate/min_perf_pct
This will force intel_pstate to select the highest P state and
leave it there.
Turbostat is useful for collecting frequency (P state) and idle (C state)
information.
--Dirk
next prev parent reply other threads:[~2013-10-25 14:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMeUXYuuM4LS2qAhhvQi8VG1bK4eiZjjTikchgHzeqi2EX6=bw@mail.gmail.com>
2013-10-24 5:28 ` powersave governor runs programs faster and uses more power than performance governor Viresh Kumar
2013-10-24 19:42 ` Melanie Kambadur
2013-10-25 14:31 ` David C Niemi
2013-10-25 14:40 ` Dirk Brandewie [this message]
2013-10-25 15:13 ` Melanie Kambadur
2013-10-25 15:38 ` Dirk Brandewie
2013-10-25 16:35 ` Melanie Kambadur
2013-10-25 18:27 ` David C Niemi
2013-10-29 16:25 ` Melanie Kambadur
2013-10-29 16:27 ` Melanie Kambadur
2013-10-29 17:03 ` Dirk Brandewie
[not found] ` <CAMeUXYswoEhNbVua6wV-qg_DL5mn5Eahdny12wvSbs02h16RBQ@mail.gmail.com>
2014-11-11 19:46 ` David C Niemi
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=526A82CC.1040709@gmail.com \
--to=dirk.brandewie@gmail.com \
--cc=cpufreq@vger.kernel.org \
--cc=dniemi@verisign.com \
--cc=linux-pm@vger.kernel.org \
--cc=melanie@cs.columbia.edu \
--cc=viresh.kumar@linaro.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).