From: "Doug Smythies" <dsmythies@telus.net>
To: 'Paul Menzel' <pmenzel@molgen.mpg.de>
Cc: linux-pm@vger.kernel.org, 'LKML' <linux-kernel@vger.kernel.org>,
'Srinivas Pandruvada' <srinivas.pandruvada@linux.intel.com>,
'Len Brown' <lenb@kernel.org>,
Doug Smythies <dsmythies@telus.net>
Subject: RE: intel_pstate: Lowest frequency not reached with Intel i7-6700
Date: Wed, 12 Dec 2018 15:06:30 -0800 [thread overview]
Message-ID: <000701d4926f$533eb270$f9bc1750$@net> (raw)
In-Reply-To: XCF0g8mvUQvFWXCF1gj1RM
On 2018.12.12 13:40 Paul Menzel wrote:
> Using *powersave* as P-state selection algorithm, on an idle system
Define "idle system".
If your computer is running a GUI, or is even a server without a GUI
but with many services running, then "idle" really isn't.
Below is from my test server, with many services disabled, so
"idle" really is quite "idle"
doug@s15:~/temp$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt --interval 15
Busy% Bzy_MHz PkgTmp PkgWatt
0.01 1608 27 3.71
0.01 1619 27 3.71
0.01 1600 28 3.71
0.01 1600 28 3.70
Note that p state 16 (1600 MHz) is the minimum for my older i7-2600k processor.
> Shouldn’t it go down until 800 MHz?
We would need some actual busy information, turbostat is the recommended tool,
to know for sure.
... Doug
next reply other threads:[~2018-12-12 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 23:06 Doug Smythies [this message]
2018-12-13 9:54 ` intel_pstate: Lowest frequency not reached with Intel i7-6700 Paul Menzel
2018-12-13 10:39 ` Rafael J. Wysocki
2018-12-13 12:41 ` Paul Menzel
2018-12-13 16:36 ` Srinivas Pandruvada
2018-12-13 16:21 ` Doug Smythies
-- strict thread matches above, loose matches on Subject: below --
2018-12-12 21:40 Paul Menzel
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='000701d4926f$533eb270$f9bc1750$@net' \
--to=dsmythies@telus.net \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=srinivas.pandruvada@linux.intel.com \
/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).