From: Peter Zijlstra <peterz@infradead.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: linux-kernel@vger.kernel.org, Mike Galbraith <efault@gmx.de>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Very high CPU values in top on idle system (3.0-rc1)
Date: Tue, 31 May 2011 11:55:45 +0200 [thread overview]
Message-ID: <1306835745.2353.3.camel@twins> (raw)
In-Reply-To: <1306793579.2530.2.camel@twins>
On Tue, 2011-05-31 at 00:12 +0200, Peter Zijlstra wrote:
>
> I poked around with some skip_rq_update bits but couldn't make it go
> away, will try more tomorrow.
Gah, that was annoying, and explains why I wasn't seeing it on my main
dev box but could see it on my desktop (wsm tsc is much better synced
than the core2 tsc).
Could you confirm that this indeed cures the problem? I'll probably
commit a version without the toggle, but that was easy for verifying it
indeed made a difference..
---
Index: linux-2.6/kernel/sched.c
===================================================================
--- linux-2.6.orig/kernel/sched.c
+++ linux-2.6/kernel/sched.c
@@ -2604,6 +2601,8 @@ static void ttwu_queue(struct task_struc
#if defined(CONFIG_SMP)
if (sched_feat(TTWU_QUEUE) && cpu != smp_processor_id()) {
+ if (sched_feat(TTWU_SYNC_CLOCK))
+ sched_clock_cpu(cpu); /* sync clocks x-cpu */
ttwu_queue_remote(p, cpu);
return;
}
Index: linux-2.6/kernel/sched_features.h
===================================================================
--- linux-2.6.orig/kernel/sched_features.h
+++ linux-2.6/kernel/sched_features.h
@@ -70,3 +70,4 @@ SCHED_FEAT(NONIRQ_POWER, 1)
* using the scheduler IPI. Reduces rq->lock contention/bounces.
*/
SCHED_FEAT(TTWU_QUEUE, 1)
+SCHED_FEAT(TTWU_SYNC_CLOCK, 1)
next prev parent reply other threads:[~2011-05-31 9:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 17:39 Very high CPU values in top on idle system (3.0-rc1) Markus Trippelsdorf
2011-05-30 18:05 ` Peter Zijlstra
2011-05-30 18:23 ` Markus Trippelsdorf
2011-05-30 20:45 ` Markus Trippelsdorf
2011-05-30 22:12 ` Peter Zijlstra
2011-05-31 9:55 ` Peter Zijlstra [this message]
2011-05-31 10:04 ` Markus Trippelsdorf
2011-05-31 12:31 ` [tip:sched/urgent] sched: Fix cross-cpu clock sync on remote wakeups tip-bot for Peter Zijlstra
2011-05-31 12:56 ` Borislav Petkov
2011-05-31 13:11 ` Peter Zijlstra
2011-06-01 7:05 ` Borislav Petkov
2011-06-01 10:36 ` Peter Zijlstra
2011-06-01 15:50 ` Borislav Petkov
2011-06-02 7:52 ` Yong Zhang
2011-06-02 13:04 ` Peter Zijlstra
2011-06-02 14:23 ` Yong Zhang
2011-06-02 15:48 ` Peter Zijlstra
2011-06-03 6:49 ` Yong Zhang
2011-06-03 9:57 ` Milton Miller
2011-06-03 10:36 ` Peter Zijlstra
2011-06-03 10:55 ` Peter Zijlstra
2011-06-03 10:58 ` Peter Zijlstra
2011-06-07 13:12 ` Borislav Petkov
2011-06-07 13:16 ` Peter Zijlstra
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=1306835745.2353.3.camel@twins \
--to=peterz@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mingo@elte.hu \
/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