From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Doug Smythies <dsmythies@telus.net>
Subject: [PATCH 0/2] cpufreq: intel_pstate: Eliminate the PID controller
Date: Tue, 25 Jul 2017 00:10:04 +0200 [thread overview]
Message-ID: <6183701.sLtcQDF8CA@aspire.rjw.lan> (raw)
Hi,
According to testing so far, the P-state selection based on the PID controller
in intel_pstate can be replaced with the P-state selection based on CPU load
with no considerable regressions *and* the PID-based P-state selection is
generally flaky and hard to manage, make intel_pstate use the P-state selection
based on CPU load for all categories of systems and eliminate the PID controller
along with all things related to it from the driver.
[1/2] is the actual elimination.
[2/2] is a simplification possible after [1/2].
Thanks,
Rafael
next reply other threads:[~2017-07-24 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 22:10 Rafael J. Wysocki [this message]
2017-07-24 22:10 ` [PATCH 1/2] cpufreq: intel_pstate: Do not use PID-based P-state selection Rafael J. Wysocki
2017-07-24 22:12 ` [PATCH 2/2] cpufreq: intel_pstate: Drop ->update_util from pstate_funcs Rafael J. Wysocki
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=6183701.sLtcQDF8CA@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=dsmythies@telus.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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
all inboxes | Powered by JetHome®