Hi.

Probably FAIR_GROUP_SCHED in config and commit 
6b2d7700266b9402e12824e11e0099ae6a4a6a79 (sched: group scheduler, fix 
fairness of cpu bandwidth allocation for task groups):
(extract)

+#ifdef CONFIG_FAIR_GROUP_SCHED
+       if (nr_cpu_ids == 1)
+               return;
+
+       lb_monitor_task = kthread_create(load_balance_monitor, NULL,
+                                        "group_balance");
+       if (!IS_ERR(lb_monitor_task)) {
+               lb_monitor_task->flags |= PF_NOFREEZE;
+               wake_up_process(lb_monitor_task);
+       } else {
+               printk(KERN_ERR "Could not create load balance monitor 
thread"
+                       "(error = %ld) \n", PTR_ERR(lb_monitor_task));
+       }
+#endif

# powertop -d
PowerTOP 1.9    (C) 2007 Intel Corporation

Sammle Daten für 15 Sekunden
Cn                 Verweildauer
C0 (Prozessor läuft)    ( 0,2%)
C1                0,0ms ( 0,0%)
C2                0,0ms ( 0,0%)
C3               23,6ms (99,8%)
P-States (Frequenzen)
  1,84 GHz   100,0%
  1,67 GHz     0,0%
  1500 MHz     0,0%
  1333 MHz     0,0%
Aufwachen pro Sekunde : 42,4    Intervall: 15,0s
Keine ACPI Stromverbrauch-Schätzung verfügbar
Häufigste Ursachen für das Aufwachen:
  28,6% ( 14,6)       <interrupt> : wifi0
  23,5% ( 12,0)   <kernel module> : usb_hcd_poll_rh_status (rh_timer_func)
  15,8% (  8,1)         amarokapp : schedule_timeout (process_timeout)
  15,1% (  7,7)     group_balance : schedule_timeout (process_timeout)
   2,2% (  1,1)            kicker : schedule_timeout (process_timeout)
   2,2% (  1,1)              kwin : schedule_timeout (process_timeout)
   2,0% (  1,0)           ifplugd : schedule_timeout (process_timeout)
   2,0% (  1,0)          kwrapper : do_nanosleep (hrtimer_wakeup)
   1,4% (  0,7)                 X : do_setitimer (it_real_fn)
   0,9% (  0,5)              kded : schedule_timeout (process_timeout)
   0,9% (  0,5)         gpg-agent : schedule_timeout (process_timeout)
   0,8% (  0,4)          kdesktop : schedule_timeout (process_timeout)
   0,7% (  0,3)      <kernel IPI> : Rescheduling interrupts
   0,4% (  0,2)           konsole : schedule_timeout (process_timeout)
   0,4% (  0,2)              init : schedule_timeout (process_timeout)
   0,4% (  0,2)         amarokapp : futex_wait (hrtimer_wakeup)
   0,4% (  0,2)                ip : __netdev_watchdog_up (dev_watchdog)
   0,4% (  0,2)              nscd : futex_wait (hrtimer_wakeup)
   0,3% (  0,1)     <kernel core> : inet_twsk_schedule (inet_twdr_hangman)
   0,3% (  0,1)     <kernel core> : neigh_table_init_no_netlink 
(neigh_periodic_timer)
   0,3% (  0,1)          kio_http : schedule_timeout (process_timeout)
   0,1% (  0,1)       <interrupt> : uhci_hcd:usb1, ehci_hcd:usb5
   0,1% (  0,1)      <kernel IPI> : function call interrupts
   0,1% (  0,1)     <kernel core> : input_handle_event (input_repeat_key)
   0,1% (  0,1)                 X : schedule_timeout (process_timeout)
   0,1% (  0,1)     <kernel core> : neigh_add_timer (neigh_timer_handler)
   0,1% (  0,1)   <kernel module> : ieee80211_node_attach 
(ieee80211_node_timeout)
   0,1% (  0,1)     <kernel core> : init_nonfatal_mce_checker 
(delayed_work_timer_fn)
   0,1% (  0,1)     <kernel core> : ip_rt_init (delayed_work_timer_fn)
   0,1% (  0,1)   USB Gerät  1-2 : Apple Internal Keyboard / Trackpad 
(Apple Computer)

Is this normal behaviour?

mfg
thomas

_______________________________________________
Power mailing list
[email protected]
http://www.bughost.org/mailman/listinfo/power

Reply via email to