From: Steve Muckle <steve.muckle@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM list <linux-pm@vger.kernel.org>,
Juri Lelli <juri.lelli@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC/RFT][PATCH v4 1/2] cpufreq: New governor using utilization data from the scheduler
Date: Wed, 2 Mar 2016 19:35:36 -0800 [thread overview]
Message-ID: <56D7B108.80101@linaro.org> (raw)
In-Reply-To: <56D7AD86.8080702@linaro.org>
On 03/02/2016 07:20 PM, Steve Muckle wrote:
> Why does the frequency value not help? It is true there may be issues of
> a workload being memory bound and not responding quite linearly to
> increasing frequency, but that would pose a problem for the current
> algorithm also. Surely it's better to attempt a consistent policy which
> doesn't vary based on a platform's fmin value?
FWIW I'm not trying to hold up this series - rather just discuss
possibilities and differences with the now deprecated solution that may
be able to be integrated here sometime in the near future.
next prev parent reply other threads:[~2016-03-03 3:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 23:16 [RFC/RFT][PATCH 0/1] cpufreq: New governor based on scheduler-provided utilization data Rafael J. Wysocki
2016-02-21 23:18 ` [RFC/RFT][PATCH 1/1] cpufreq: New governor using utilization data from the scheduler Rafael J. Wysocki
2016-02-22 14:16 ` Juri Lelli
2016-02-22 23:02 ` Rafael J. Wysocki
2016-02-23 7:20 ` Steve Muckle
2016-02-24 1:38 ` Rafael J. Wysocki
2016-02-25 11:01 ` Juri Lelli
2016-02-26 2:36 ` Rafael J. Wysocki
2016-03-01 14:56 ` Juri Lelli
2016-03-01 20:26 ` Rafael J. Wysocki
2016-02-24 1:20 ` [RFC/RFT][PATCH v2 0/2] cpufreq: New governor based on scheduler-provided utilization data Rafael J. Wysocki
2016-02-24 1:22 ` [RFC/RFT][PATCH v2 1/2] cpufreq: New governor using utilization data from the scheduler Rafael J. Wysocki
2016-02-25 21:14 ` [RFC/RFT][PATCH v4 " Rafael J. Wysocki
2016-02-27 0:21 ` Rafael J. Wysocki
2016-02-27 4:33 ` Steve Muckle
2016-02-27 15:24 ` Rafael J. Wysocki
2016-03-01 4:10 ` Steve Muckle
2016-03-01 20:20 ` Rafael J. Wysocki
2016-03-03 3:20 ` Steve Muckle
2016-03-03 3:35 ` Steve Muckle [this message]
2016-03-03 19:20 ` Rafael J. Wysocki
2016-02-24 1:28 ` [RFC/RFT][PATCH v2 2/2] cpufreq: schedutil: Switching frequencies from interrupt context Rafael J. Wysocki
2016-02-24 23:30 ` [RFC/RFT][PATCH v3 " Rafael J. Wysocki
2016-02-25 9:08 ` Peter Zijlstra
2016-02-25 9:12 ` Peter Zijlstra
2016-02-25 11:11 ` Rafael J. Wysocki
2016-02-25 11:10 ` Rafael J. Wysocki
2016-02-25 11:52 ` Peter Zijlstra
2016-02-25 20:54 ` Rafael J. Wysocki
2016-02-25 21:20 ` [RFC/RFT][PATCH v4 " Rafael J. Wysocki
2016-03-03 14:27 ` [RFC/RFT][PATCH 0/1] cpufreq: New governor based on scheduler-provided utilization data Ingo Molnar
2016-03-03 17:15 ` 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=56D7B108.80101@linaro.org \
--to=steve.muckle@linaro.org \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--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).