From: Dario Faggioli <raistlin@linux.it>
To: Harald Gustafsson <hgu1972@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Harald Gustafsson <harald.gustafsson@ericsson.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Claudio Scordino <claudio@evidence.eu.com>,
Michael Trimarchi <trimarchi@retis.sssup.it>,
Fabio Checconi <fabio@gandalf.sssup.it>,
Tommaso Cucinotta <cucinotta@sssup.it>,
Juri Lelli <juri.lelli@gmail.com>
Subject: Re: [PATCH 1/3] Added runqueue clock normalized with cpufreq
Date: Fri, 17 Dec 2010 19:48:18 +0100 [thread overview]
Message-ID: <1292611698.2697.61.camel@Palantir> (raw)
In-Reply-To: <AANLkTi=L9KB_P62Rn7kpuMxbSNnE9U4+EZK6nwqFZ-x7@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
On Fri, 2010-12-17 at 16:02 +0100, Harald Gustafsson wrote:
> > Once you have a governor that keeps the freq such that: freq/max_freq >=
> > utilization (which is only sufficient for deadline == period systems),
> > then you need to frob the SCHED_DEADLINE runtime accounting.
>
> I agree that this is the other part of the solution, which I have in a separate
> ondemand governor, but that code is not ready for public review yet. Since that
> code also incorporate other ondemand changes I'm playing with.
>
So, while we're waiting for this to be cooked...
> OK, I can do that. My thought from the beginning was considering that
> the reading of the clock was done more often then updating it, but I agree that
> it has a negative impact on none dl threads.
>
... We can at least integrate this (done in the proper, way as Peter
suggests, i.e., _inside_ SCHED_DEADLINE) in the next release of the
patchset, can't we?
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
----------------------------------------------------------------------
Dario Faggioli, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy)
http://retis.sssup.it/people/faggioli -- dario.faggioli@jabber.org
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-12-17 18:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 13:02 [PATCH 1/3] Added runqueue clock normalized with cpufreq Harald Gustafsson
2010-12-17 13:02 ` [PATCH 2/3] cpufreq normalized runtime to enforce runtime cycles also at lower frequencies Harald Gustafsson
2010-12-17 13:02 ` [PATCH 3/3] sched trace updated with normalized clock info Harald Gustafsson
2010-12-17 14:29 ` [PATCH 1/3] Added runqueue clock normalized with cpufreq Peter Zijlstra
2010-12-17 14:32 ` Peter Zijlstra
2010-12-17 15:06 ` Harald Gustafsson
2010-12-17 15:16 ` Peter Zijlstra
2010-12-17 15:36 ` Harald Gustafsson
2010-12-17 15:43 ` Thomas Gleixner
2010-12-17 15:54 ` Harald Gustafsson
2010-12-17 18:44 ` Dario Faggioli
2011-01-03 14:17 ` Pavel Machek
2010-12-17 15:02 ` Harald Gustafsson
2010-12-17 18:48 ` Dario Faggioli [this message]
2010-12-17 18:56 ` Dario Faggioli
2010-12-17 18:59 ` Peter Zijlstra
2010-12-17 19:16 ` Dario Faggioli
2010-12-17 19:31 ` Harald Gustafsson
2010-12-20 0:11 ` Tommaso Cucinotta
2010-12-20 9:44 ` Harald Gustafsson
2011-01-03 20:25 ` Tommaso Cucinotta
2011-01-04 12:16 ` Harald Gustafsson
2010-12-17 19:27 ` Harald Gustafsson
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=1292611698.2697.61.camel@Palantir \
--to=raistlin@linux.it \
--cc=claudio@evidence.eu.com \
--cc=cucinotta@sssup.it \
--cc=fabio@gandalf.sssup.it \
--cc=harald.gustafsson@ericsson.com \
--cc=hgu1972@gmail.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=trimarchi@retis.sssup.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.