From: Alex Shi <alex.shi@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>, daniel.lezcano@linaro.org
Cc: mingo@redhat.com, tglx@linutronix.de, vincent.guittot@linaro.org,
morten.rasmussen@arm.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, fengguang.wu@intel.com,
linaro-kernel@lists.linaro.org
Subject: Re: [RFC PATCH] sched: find the latest idle cpu
Date: Wed, 15 Jan 2014 22:37:56 +0800 [thread overview]
Message-ID: <52D69D44.4090504@linaro.org> (raw)
In-Reply-To: <20140115073533.GU31570@twins.programming.kicks-ass.net>
On 01/15/2014 03:35 PM, Peter Zijlstra wrote:
> On Wed, Jan 15, 2014 at 12:07:59PM +0800, Alex Shi wrote:
>> Currently we just try to find least load cpu. If some cpus idled,
>> we just pick the first cpu in cpu mask.
>>
>> In fact we can get the interrupted idle cpu or the latest idled cpu,
>> then we may get the benefit from both latency and power.
>> The selected cpu maybe not the best, since other cpu may be interrupted
>> during our selecting. But be captious costs too much.
>
> No, we should not do anything like this without first integrating
> cpuidle.
>
> At which point we have a sane view of the idle states and can make a
> sane choice between them.
>
Daniel,
Any comments to make it better?
--
Thanks
Alex
next prev parent reply other threads:[~2014-01-15 14:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 4:07 [RFC PATCH] sched: find the latest idle cpu Alex Shi
2014-01-15 4:31 ` Michael wang
2014-01-15 4:48 ` Alex Shi
2014-01-15 4:53 ` Alex Shi
2014-01-15 5:06 ` Alex Shi
2014-01-15 5:33 ` Michael wang
2014-01-15 6:45 ` Alex Shi
2014-01-15 8:05 ` Michael wang
2014-01-15 14:28 ` Alex Shi
2014-01-15 7:35 ` Peter Zijlstra
2014-01-15 14:37 ` Alex Shi [this message]
2014-01-16 11:03 ` Daniel Lezcano
2014-01-16 11:38 ` Peter Zijlstra
2014-01-16 12:16 ` Daniel Lezcano
2014-01-17 2:40 ` Nicolas Pitre
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=52D69D44.4090504@linaro.org \
--to=alex.shi@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=daniel.lezcano@linaro.org \
--cc=fengguang.wu@intel.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).