From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Amit Kucheria <amit.kucheria@linaro.org>,
linux-kernel@vger.kernel.org,
LAK <linux-arm-kernel@lists.infradead.org>,
linaro-dev@lists.linaro.org,
Srivatsa Vaddagiri <vatsa@in.ibm.com>,
Venkatesh Pallipadi <venki@google.com>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Ingo Molnar <mingo@elte.hu>, Paul Turner <pjt@google.com>
Subject: Re: sched: ARM: arch_scale_freq_power
Date: Tue, 11 Oct 2011 18:21:15 +0200 [thread overview]
Message-ID: <1318350075.14615.9.camel@twins> (raw)
In-Reply-To: <CAKfTPtDgKcTucAR-YW27boAeUu1Ur6Txw6hLm3B48jw+sgEUOw@mail.gmail.com>
On Tue, 2011-10-11 at 18:03 +0200, Vincent Guittot wrote:
> > How do you know the task is 'small' ?
> >
>
> I want to use cpufreq to be notified that we have a large/small cpu
> load. If we have several tasks but the cpu uses the lowest frequency,
> it "should" mean that we have small tasks that are running (less than
> 20ms*95% of added duration) and we could gather them on one cpu (by
> increasing the cpu_power on a dual core).
>
> > For that you would need to track a time-weighted effective load average
> > of the task and we don't have that.
> >
>
> yes, that's why I use cpufreq until better option, like a
> time-weighted load average, is available
Egads... so basically you're (ab)using the ondemand cpufreq stats to get
a guestimate of the time-weighted load of the cpu, and then (ab)use the
scheduler cpufreq hook to pump its capacity numbers.
No cookies for you.
prev parent reply other threads:[~2011-10-11 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 11:36 sched: ARM: arch_scale_freq_power Vincent Guittot
2011-10-11 7:16 ` Amit Kucheria
2011-10-11 7:57 ` Peter Zijlstra
2011-10-11 8:51 ` Vincent Guittot
2011-10-11 9:13 ` Peter Zijlstra
2011-10-11 9:38 ` Amit Kucheria
2011-10-11 10:03 ` Peter Zijlstra
2011-10-11 9:40 ` Vincent Guittot
2011-10-11 10:27 ` Peter Zijlstra
2011-10-11 16:03 ` Vincent Guittot
2011-10-11 16:21 ` Peter Zijlstra [this message]
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=1318350075.14615.9.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=amit.kucheria@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pjt@google.com \
--cc=suresh.b.siddha@intel.com \
--cc=vatsa@in.ibm.com \
--cc=venki@google.com \
--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