Re: [PATCH] Speedup divides by cpu_power in scheduler

2007-02-22 Thread Ingo Molnar
* Eric Dumazet <[EMAIL PROTECTED]> wrote: > I noticed expensive divides done in try_to_wakeup() and > find_busiest_group() on a bi dual core Opteron machine (total of 4 > cores), moderatly loaded (15.000 context switch per second) > > oprofile numbers : nice patch! Ack for -mm testing:

Re: [PATCH] Speedup divides by cpu_power in scheduler

2007-02-22 Thread Ingo Molnar
* Eric Dumazet [EMAIL PROTECTED] wrote: I noticed expensive divides done in try_to_wakeup() and find_busiest_group() on a bi dual core Opteron machine (total of 4 cores), moderatly loaded (15.000 context switch per second) oprofile numbers : nice patch! Ack for -mm testing: Acked-by:

[PATCH] Speedup divides by cpu_power in scheduler

2007-02-21 Thread Eric Dumazet
I noticed expensive divides done in try_to_wakeup() and find_busiest_group() on a bi dual core Opteron machine (total of 4 cores), moderatly loaded (15.000 context switch per second) oprofile numbers : CPU: AMD64 processors, speed 2600.05 MHz (estimated) Counted CPU_CLK_UNHALTED events

[PATCH] Speedup divides by cpu_power in scheduler

2007-02-21 Thread Eric Dumazet
I noticed expensive divides done in try_to_wakeup() and find_busiest_group() on a bi dual core Opteron machine (total of 4 cores), moderatly loaded (15.000 context switch per second) oprofile numbers : CPU: AMD64 processors, speed 2600.05 MHz (estimated) Counted CPU_CLK_UNHALTED events