From: Alex Shi <alex.shi@linaro.org>
To: Michael wang <wangyun@linux.vnet.ibm.com>,
mingo@redhat.com, peterz@infradead.org, tglx@linutronix.de,
daniel.lezcano@linaro.org, vincent.guittot@linaro.org,
morten.rasmussen@arm.com
Cc: 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 12:48:51 +0800 [thread overview]
Message-ID: <52D61333.8060705@linaro.org> (raw)
In-Reply-To: <52D60F11.3070005@linux.vnet.ibm.com>
On 01/15/2014 12:31 PM, Michael wang wrote:
> Hi, Alex
>
> On 01/15/2014 12:07 PM, Alex Shi wrote:
> [snip] }
>> +#ifdef CONFIG_NO_HZ_COMMON
>> + /*
>> + * Coarsely to get the latest idle cpu for shorter latency and
>> + * possible power benefit.
>> + */
>> + if (!min_load) {
here should be !load.
>> + struct tick_sched *ts = &per_cpu(tick_cpu_sched, i);
>> +
>> + s64 latest_wake = 0;
>
> I guess we missed some code for latest_wake here?
Yes, thanks for reminder!
so updated patch:
====
>From c3a88e73fed3da96549b5a922076e996832685f8 Mon Sep 17 00:00:00 2001
From: Alex Shi <alex.shi@linaro.org>
Date: Tue, 14 Jan 2014 23:07:42 +0800
Subject: [PATCH] sched: find the latest idle cpu
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.
Signed-off-by: Alex Shi <alex.shi@linaro.org>
---
kernel/sched/fair.c | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index c7395d9..73a2a07 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -4167,6 +4167,31 @@ find_idlest_cpu(struct sched_group *group, struct task_struct *p, int this_cpu)
min_load = load;
idlest = i;
}
+#ifdef CONFIG_NO_HZ_COMMON
+ /*
+ * Coarsely to get the latest idle cpu for shorter latency and
+ * possible power benefit.
+ */
+ if (!load) {
+ struct tick_sched *ts = &per_cpu(tick_cpu_sched, i);
+
+ s64 latest_wake = 0;
+ /* idle cpu doing irq */
+ if (ts->inidle && !ts->idle_active)
+ idlest = i;
+ /* the cpu resched */
+ else if (!ts->inidle)
+ idlest = i;
+ /* find latest idle cpu */
+ else {
+ s64 temp = ktime_to_us(ts->idle_entrytime);
+ if (temp > latest_wake) {
+ latest_wake = temp;
+ idlest = i;
+ }
+ }
+ }
+#endif
}
return idlest;
--
1.8.1.2
--
Thanks
Alex
next prev parent reply other threads:[~2014-01-15 4:49 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 [this message]
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
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=52D61333.8060705@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 \
--cc=wangyun@linux.vnet.ibm.com \
/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).