public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: Rescheduling interrupts
Date: Tue, 22 Jan 2008 18:11:24 +0200	[thread overview]
Message-ID: <200801221811.25867.caglar@pardus.org.tr> (raw)
In-Reply-To: <20080122160557.GA31831@elte.hu>

22 Oca 2008 Sal tarihinde, Ingo Molnar şunları yazmıştı: 
> 
> * 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.

Heh, killing amarok ends up with following;

     PowerTOP version 1.9       (C) 2007 Intel Corporation

Cn                Avg residency       P-states (frequencies)
C0 (cpu running)        ( 0,9%)
C1                0,0ms ( 0,0%)
C2                0,2ms ( 0,0%)
C3                5,1ms (99,1%)


Wakeups-from-idle per second : 197,8    interval: 10,0s
no ACPI power usage estimate available

Top causes for wakeups:
  34,7% (130,7)   USB device  3-2 : HP Integrated Module (Broadcom Corp)
  26,5% (100,0)       <interrupt> : uhci_hcd:usb3
   5,8% ( 22,0)              java : futex_wait (hrtimer_wakeup)
   5,3% ( 20,0)       <interrupt> : iwl3945
   4,1% ( 15,4)   USB device  2-2 : Microsoft Wireless Optical Mouse .00 (Microsoft)
   2,9% ( 11,0)       <interrupt> : libata
   2,7% ( 10,1)       <interrupt> : extra timer interrupt
   2,7% ( 10,0)              java : schedule_timeout (process_timeout)
   2,7% ( 10,0)     <kernel core> : scan_async (ehci_watchdog)
   2,4% (  9,0)      <kernel IPI> : Rescheduling interrupts
   2,1% (  8,0)   <kernel module> : usb_hcd_poll_rh_status (rh_timer_func)
   1,7% (  6,4)       <interrupt> : uhci_hcd:usb2
   1,7% (  6,4)             artsd : schedule_timeout (process_timeout)
   0,6% (  2,1)       <interrupt> : ohci1394, uhci_hcd:usb4, nvidia
   0,5% (  2,0)     <kernel core> : clocksource_check_watchdog (clocksource_watchdog)
   0,5% (  1,7)    wpa_supplicant : schedule_timeout (process_timeout)
   0,3% (  1,0)            kicker : schedule_timeout (process_timeout)
   0,3% (  1,0)              kwin : schedule_timeout (process_timeout)
   0,3% (  1,0)          kdesktop : schedule_timeout (process_timeout)
   0,3% (  1,0)           klipper : schedule_timeout (process_timeout)
   0,3% (  1,0)          kwrapper : do_nanosleep (hrtimer_wakeup)
   0,3% (  1,0)                 X : nv_start_rc_timer (nv_kern_rc_timer)

-- 
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!

  reply	other threads:[~2008-01-22 16:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 23:19 Rescheduling interrupts 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 [this message]
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

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=200801221811.25867.caglar@pardus.org.tr \
    --to=caglar@pardus.org.tr \
    --cc=arjan@linux.intel.com \
    --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