From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Steve Muckle <steve.muckle@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Juri Lelli <Juri.Lelli@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Doug Smythies <doug.smythies@gmail.com>
Subject: Re: [RFC/RFT][PATCH 0/4] cpufreq / sched: iowait boost in intel_pstate and schedutil
Date: Wed, 07 Sep 2016 17:35:50 -0700 [thread overview]
Message-ID: <1473294950.154359.38.camel@linux.intel.com> (raw)
In-Reply-To: <20160908002226.GC15431@graphite.smuckle.net>
On Wed, 2016-09-07 at 17:22 -0700, Steve Muckle wrote:
> On Sat, Sep 03, 2016 at 02:56:48AM +0200, Rafael J. Wysocki wrote:
> >
> > Please let me know what you think and if you can run some
> > benchmarks you
> > care about and see if the changes make any difference (this way or
> > another),
> > please do that and let me know what you've found.
>
> LGTM (I just reviewed the first and last patch, skipping the
> intel_pstate ones).
>
> I was unable to see a conclusive power regression in Android audio,
> video or
> idle usecases on my hikey 96board.
Did you see any performance regression on Android workloads?
Thanks,
Srinivas
>
> thanks,
> Steve
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-09-08 0:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 0:56 [RFC/RFT][PATCH 0/4] cpufreq / sched: iowait boost in intel_pstate and schedutil Rafael J. Wysocki
2016-09-03 0:58 ` [RFC/RFT][PATCH 1/4] cpufreq / sched: SCHED_CPUFREQ_IOWAIT flag to indicate iowait condition Rafael J. Wysocki
2016-09-03 1:02 ` [RFC/RFT][PATCH 2/4] cpufreq: intel_pstate: Change P-state selection algorithm for Core Rafael J. Wysocki
2016-09-03 1:03 ` [RFC/RFT][PATCH 3/4] cpufreq: intel_pstate: Use average P-state in get_target_pstate_default() Rafael J. Wysocki
2016-09-03 1:04 ` [RFC/RFT][PATCH 4/4] cpufreq: schedutil: Add iowait boosting Rafael J. Wysocki
2016-09-07 15:26 ` [RFC/RFT][PATCH 2/4] cpufreq: intel_pstate: Change P-state selection algorithm for Core Doug Smythies
2016-09-08 0:22 ` [RFC/RFT][PATCH 0/4] cpufreq / sched: iowait boost in intel_pstate and schedutil Steve Muckle
2016-09-08 0:35 ` Srinivas Pandruvada [this message]
2016-09-08 0:44 ` Rafael J. Wysocki
2016-09-08 0:49 ` Srinivas Pandruvada
2016-09-08 1:15 ` Rafael J. Wysocki
2016-09-08 15:02 ` Rafael J. Wysocki
2016-09-08 17:30 ` Srinivas Pandruvada
2016-09-08 19:26 ` Steve Muckle
2016-09-08 19:49 ` Srinivas Pandruvada
2016-09-08 0:37 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2016-09-04 15:54 Doug Smythies
2016-09-04 23:54 ` Rafael J. Wysocki
2016-09-07 15:25 ` Doug Smythies
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=1473294950.154359.38.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=Juri.Lelli@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=doug.smythies@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=steve.muckle@linaro.org \
--cc=vincent.guittot@linaro.org \
--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).