From: Peter Zijlstra <peterz@infradead.org>
To: Morten Rasmussen <morten.rasmussen@arm.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"mingo@kernel.org" <mingo@kernel.org>,
"markgross@thegnar.org" <markgross@thegnar.org>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [3/11] issue 3: No understanding of potential cpu capacity
Date: Tue, 14 Jan 2014 17:51:19 +0100 [thread overview]
Message-ID: <20140114165119.GJ7572@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <20140114163953.GF3000@e103034-lin>
On Tue, Jan 14, 2014 at 04:39:54PM +0000, Morten Rasmussen wrote:
> Responsiveness is still very important. It is quite hard to control. CFS
> doesn't consider latency. The only way to get the best responsiveness is
> to go for best performance which comes at a high cost in energy.
The big problem is that the normal unix task model doesn't cover his at
all -- nice isn't much of a knob.
There's ways in which you can adapt CFS to include such a measure
(search for the EEVDF patches), but I was kinda hoping that tasks that
really desire responsiveness could be made to use SCHED_DEADLINE or
such.
next prev parent reply other threads:[~2014-01-14 16:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 16:19 [0/11][REPOST] Energy-aware scheduling use-cases and scheduler issues Morten Rasmussen
2014-01-07 16:19 ` [1/11] issue 1: Missing power topology information in scheduler Morten Rasmussen
2014-01-07 16:19 ` [2/11] issue 2: Energy-awareness for heterogeneous systems Morten Rasmussen
2014-01-07 16:19 ` [3/11] issue 3: No understanding of potential cpu capacity Morten Rasmussen
2014-01-13 21:07 ` Rafael J. Wysocki
2014-01-14 10:27 ` Peter Zijlstra
2014-01-14 16:39 ` Morten Rasmussen
2014-01-14 16:51 ` Peter Zijlstra [this message]
2014-01-07 16:19 ` [4/11] issue 4: Tracking idle states Morten Rasmussen
2014-01-07 16:19 ` [5/11] issue 5: Frequency and uarch invariant task load Morten Rasmussen
2014-01-08 12:31 ` Peter Zijlstra
2014-01-16 11:16 ` Morten Rasmussen
2014-01-07 16:19 ` [6/11] issue 6: Poor and non-deterministic performance on heterogeneous systems Morten Rasmussen
2014-01-07 16:19 ` [7/11] use-case 1: Webbrowsing on Android Morten Rasmussen
2014-01-07 16:19 ` [8/11] use-case 2: Audio playback " Morten Rasmussen
2014-01-07 16:19 ` [9/11] use-case 3: Video " Morten Rasmussen
2014-01-07 16:19 ` [10/11] use-case 4: Game " Morten Rasmussen
2014-01-07 16:19 ` [11/11] system 1: Saving energy using DVFS Morten Rasmussen
2014-01-20 16:32 ` Pavel Machek
2014-01-21 12:14 ` Morten Rasmussen
2014-01-21 12:31 ` Pavel Machek
2014-01-20 16:49 ` Pavel Machek
2014-01-20 17:10 ` Catalin Marinas
2014-01-20 17:17 ` Catalin Marinas
2014-01-20 17:47 ` Pavel Machek
2014-01-20 18:03 ` Catalin Marinas
2014-01-20 19:15 ` Pavel Machek
2014-01-21 11:19 ` Catalin Marinas
2014-01-20 17:54 ` Pavel Machek
2014-01-20 18:16 ` Catalin Marinas
2014-01-20 20:44 ` Pavel Machek
2014-01-20 18:25 ` Sebastian Reichel
2014-01-21 18:53 ` Kalle Jokiniemi
2014-01-20 18:12 ` Pavel Machek
2014-01-21 11:42 ` Catalin Marinas
2014-01-21 12:20 ` Pavel Machek
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=20140114165119.GJ7572@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Catalin.Marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=markgross@thegnar.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=rjw@rjwysocki.net \
--cc=vincent.guittot@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
Powered by JetHome