mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM list <linux-pm@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	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>,
	Steve Muckle <smuckle@linaro.org>,
	Doug Smythies <doug.smythies@gmail.com>
Subject: [PATCH 0/3] cpufreq / sched: iowait boost in intel_pstate and schedutil
Date: Fri, 09 Sep 2016 23:57:21 +0200	[thread overview]
Message-ID: <21371892.ALJNnHKoBY@vostro.rjw.lan> (raw)

Hi Everyone,

This is a new iteration of the "iowait boost" series.

The first two patches (adding the SCHED_CPUFREQ_IOWAIT flag and changing
schedutil to use it) don't seem to be controversial, so they go unchanged
(not RFC any more though) and the only difference is the intel_pstate
part.

Since we still get some unconclusive results with the new algorithm
for Core processors, patch [3/3] in this series modifies the Atom
algorithm to use SCHED_CPUFREQ_IOWAIT instead of the get_cpu_iowait_time_us()
interface (which isn't particularly reliable) as the first step.

Going forward we would like to modify intel_pstate to select P-states
proportional to utilization (with IOwait boosting and possibly some other
tweaks) on all processors, but there still are some factors to determine
in that area, so let's make this simple change to start with.

Thanks,
Rafael

             reply	other threads:[~2016-09-09 21:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 21:57 Rafael J. Wysocki [this message]
2016-09-09 21:59 ` [Resend][PATCH 1/3] cpufreq / sched: SCHED_CPUFREQ_IOWAIT flag to indicate iowait condition Rafael J. Wysocki
2016-09-13  7:34   ` Peter Zijlstra
2016-09-09 22:00 ` [Resend][PATCH 2/3] cpufreq: schedutil: Add iowait boosting Rafael J. Wysocki
2016-09-13  7:44   ` Peter Zijlstra
2016-09-09 22:02 ` [PATCH 3/3] cpufreq: intel_pstate: Use IOWAIT flag in Atom algorithm Rafael J. Wysocki
2016-09-13 23:59   ` [Update][PATCH " 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=21371892.ALJNnHKoBY@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --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=smuckle@linaro.org \
    --cc=srinivas.pandruvada@linux.intel.com \
    --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
all inboxes | Powered by JetHome®