From: Morten Rasmussen <morten.rasmussen@arm.com>
To: peterz@infradead.org, mingo@kernel.org
Cc: rjw@rjwysocki.net, markgross@thegnar.org,
vincent.guittot@linaro.org, catalin.marinas@arm.com,
morten.rasmussen@arm.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [0/11][REPOST] Energy-aware scheduling use-cases and scheduler issues
Date: Tue, 7 Jan 2014 16:19:36 +0000 [thread overview]
Message-ID: <1389111587-5923-1-git-send-email-morten.rasmussen@arm.com> (raw)
Reposting the series with LKML on cc as well.
Original thread (with a few replies) can be found here:
http://article.gmane.org/gmane.linux.power-management.general/41501
Sorry for double-posting.
Morten
------------------------------------------------------------------------
Hi,
One of the requests from the scheduler maintainers at the Energy-aware
Scheduling workshop at Kernel Summit this year was to provide plain text
descriptions of use-cases (workloads) and system topologies. To get that
moving I have written some short texts about some use-cases. In addition
I described a list of issues that today prevent mainly the scheduler
from achieving a good energy/performance balance in common use-cases.
The follow-up emails are structured as follows:
1-6: Current issues related to energy/performance balance.
7-10: Use-cases (overall behaviour and energy/performance goals)
11: DVFS example (for reference)
I'm hoping that this provides some of the background for why I'm
interested in improving energy-awareness in the scheduler. I'm aware
that the use-cases and issues/wishlist don't cover everyone's area of
interest. Input is needed to fix that.
Comments and input are appreciated.
Morten
next reply other threads:[~2014-01-07 16:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 16:19 Morten Rasmussen [this message]
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
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=1389111587-5923-1-git-send-email-morten.rasmussen@arm.com \
--to=morten.rasmussen@arm.com \
--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=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®