From: "Doug Smythies" <dsmythies@telus.net>
To: "'Srinivas Pandruvada'" <srinivas.pandruvada@linux.intel.com>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<x86@kernel.org>, <rjw@rjwysocki.net>, <viresh.kumar@linaro.org>,
<lenb@kernel.org>, <bp@alien8.de>, <tglx@linutronix.de>,
<mingo@redhat.com>, <hpa@zytor.com>, <peterz@infradead.org>
Subject: RE: [PATCH v4 2/2] cpufreq: intel_pstate: Allow raw energy performance preference value
Date: Tue, 30 Jun 2020 11:40:24 -0700 [thread overview]
Message-ID: <002301d64f0d$ee4bea10$cae3be30$@net> (raw)
In-Reply-To: <20200626183401.1495090-3-srinivas.pandruvada@linux.intel.com>
Hi Srinivas,
Thanks for all your work on this.
I have fallen behind, and not sure when I can catch up.
However...
On 2020.06.26 11:34 Srinivas Pandruvada wrote:
> Similarly on battery the default "balance_performance" mode can be
> aggressive in power consumption. But picking up the next choice
> "balance power" results in too much loss of performance, which results in
> bad user experience in use cases like "Google Hangout". It was observed
> that some value between these two EPP is optimal.
There is a possibility that one of the issues I have been ranting
about could be a contributing factor to things like this.
(I don't know if it actually is.)
One way to compensate is to lower EPP.
I am going to send a new e-mail in a minute about it.
Please consider the possibility that some of these
EPP adjustments might just be programming around the issue.
... Doug
next prev parent reply other threads:[~2020-06-30 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 18:33 [PATCH v4 0/2] cpufreq: intel_pstate: Support raw epp and energy_efficiency Srinivas Pandruvada
2020-06-26 18:34 ` [PATCH v4 1/2] cpufreq: intel_pstate: Allow enable/disable energy efficiency Srinivas Pandruvada
2020-06-26 18:34 ` [PATCH v4 2/2] cpufreq: intel_pstate: Allow raw energy performance preference value Srinivas Pandruvada
2020-06-30 18:40 ` Doug Smythies [this message]
2020-06-30 18:35 ` [PATCH v4 0/2] cpufreq: intel_pstate: Support raw epp and energy_efficiency 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='002301d64f0d$ee4bea10$cae3be30$@net' \
--to=dsmythies@telus.net \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).