From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "S.Çağlar Onur" <caglar@pardus.org.tr>,
LKML <linux-kernel@vger.kernel.org>,
"Arjan van de Ven" <arjan@linux.intel.com>
Subject: Re: Rescheduling interrupts
Date: Tue, 13 May 2008 21:04:05 +0200 [thread overview]
Message-ID: <19f34abd0805131204y5a3f32c0ya137c0f6e4bfa386@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0805131103q136e28ddg359de5822b401e0c@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1990 bytes --]
On Tue, May 13, 2008 at 8:03 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:> Hi,>>> On Tue, Jan 22, 2008 at 6:05 PM, Ingo Molnar <mingo@elte.hu> wrote:> >> > * S.ÃaÄlar Onur <caglar@pardus.org.tr> wrote:> >> >> > > > My theory is that for whatever reason we get "repeat" IPIs: multiple> > > > reschedule IPIs although the other CPU only initiated one.> > >> > > Ok, please see http://cekirdek.pardus.org.tr/~caglar/dmesg.3rd :)> >> > hm, the IPI sending and receiving is nicely paired up:> >> > [ 625.795008] IPI (@smp_reschedule_interrupt) from task swapper:0 on CPU#1:> > [ 625.795223] IPI (@native_smp_send_reschedule) from task amarokapp:2882 on CPU#1:> >> > amarokapp does wake up threads every 20 microseconds - that could> > explain it. It's probably Xorg running on one core, amarokapp on the> > other core. That's already 100 reschedules/sec.>> Was this IPI thing ever resolved/fixed? I'm seeing the exact same> thing on my newest Fedora 8 kernel (2.6.24.5-85.fc8) now:>> 33.3% (334.0) <kernel IPI> : Rescheduling interrupts>> And I know for sure that this did not show up a couple of months back.>> If the cause of this is known, please let me know about it. If it> isn't, I will start a bisect run now :-)
Ok -- just a confirmation. I have this on v2.6.26-rc1:
Running only init=/bin/sh (from busybox) and powertop shows:kernel IPI : Rescheduling interrupts
completely idle box (except powertop): 1 wakeups/secone busy-loop[1]: 2 wakeups/sectwo busy-loops: 500 wakeups/sec
So it seems like a real bug to me.
Vegard
[1]: while true; do echo hi; done
-- "The animistic metaphor of the bug that maliciously sneaked in whilethe programmer was not looking is intellectually dishonest as itdisguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
prev parent reply other threads:[~2008-05-13 19:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 23:19 S.Çağlar Onur
2008-01-22 10:57 ` Ingo Molnar
2008-01-22 12:55 ` S.Çağlar Onur
2008-01-22 15:23 ` Ingo Molnar
2008-01-22 15:37 ` Ingo Molnar
2008-01-22 16:00 ` S.Çağlar Onur
2008-01-22 15:55 ` S.Çağlar Onur
2008-01-22 16:05 ` Ingo Molnar
2008-01-22 16:11 ` S.Çağlar Onur
2008-01-22 16:22 ` S.Çağlar Onur
2008-01-22 17:03 ` Matt Mackall
2008-01-22 19:27 ` Ingo Molnar
[not found] ` <p73fxwoncs4.fsf@crumb.suse.de>
2008-01-23 15:52 ` Matt Mackall
2008-05-13 18:03 ` Vegard Nossum
2008-05-13 19:04 ` Vegard Nossum [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=19f34abd0805131204y5a3f32c0ya137c0f6e4bfa386@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=arjan@linux.intel.com \
--cc=caglar@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®