Kworker 和 SignalSender 是什么?为什么它们占用这么多 CPU?Powertop 的统计数据给出了这些数字。我该如何优化它?
Top causes for wakeups:
28.4% (420.4) PS/2 keyboard/mouse/touchpad interrupt
14.8% (219.5) [kernel scheduler] Load balancing tick
14.0% (206.8) kworker/0:0
8.4% (124.9) SignalSender
7.7% (114.5) [Rescheduling interrupts] <kernel IPI>
核心:
Kernel version - Linux xyz-xx-xx-110-1100 2.6.38-11-generic #48-Ubuntu SMP
Fri Jul 29 19:05:14 UTC 2011 i686 i686 i386 GNU/Linux
PowerTop 统计数据
Top causes for wakeups:
18.5% (203.6) [kernel scheduler] Load balancing tick
18.5% (203.5) kworker/0:0
16.1% (176.6) [Rescheduling interrupts] <kernel IPI>
14.2% (156.2) SignalSender
9.4% (103.5) [uhci_hcd:usb5, eth1, i915] <interrupt>
8.6% ( 94.5)D chromium-browse
4.4% ( 48.8) compiz
3.8% ( 41.5) alsa-sink
3.4% ( 37.7) icecast
0.6% ( 6.1) Xorg
0.5% ( 6.0) nginx
0.5% ( 5.1) [Function call interrupts] <kernel IPI>
0.5% ( 5.0) syndaemon
0.4% ( 4.1) [ahci] <interrupt>
0.1% ( 1.0) [hda_intel] <interrupt>
答案1
似乎与 Chromium 和 Google Chrome 有关这个问题。该问题似乎已在 Chromium 14.0.817 中得到修复。不确定何时会出现在 Google Chrome 中。