john stultz b2d9323d13 Use num_possible_cpus() instead of NR_CPUS for timer distribution ... To avoid lock contention, we distribute the sched_timer calls across the cpus so they do not trigger at the same instant. However, I used NR_CPUS, which can cause needless grouping on small smp systems depending on your kernel config. This patch converts to using num_possible_cpus() so we spread it as evenly as possible on every machine. Briefly tested w/ NR_CPUS=255 and verified reduced contention. Signed-off-by: John Stultz <johnstul@us.ibm.com> Acked-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2007-10-17 08:42:53 -07:00
..
Kconfig	clockevents: Allow build w/o run-tine usage for migration purposes	2007-10-12 23:04:05 +02:00
Makefile	clockevents: Allow build w/o run-tine usage for migration purposes	2007-10-12 23:04:05 +02:00
clockevents.c	clockevents: Allow build w/o run-tine usage for migration purposes	2007-10-12 23:04:05 +02:00
clocksource.c	…
jiffies.c	…
ntp.c	…
tick-broadcast.c	time: simplify smp_call_function_single() call sequence	2007-10-17 08:42:48 -07:00
tick-common.c	clockevents: introduce force broadcast notifier	2007-10-14 22:57:45 +02:00
tick-internal.h	…
tick-oneshot.c	…
tick-sched.c	Use num_possible_cpus() instead of NR_CPUS for timer distribution	2007-10-17 08:42:53 -07:00
timekeeping.c	kernel/time/timekeeping.c: cleanups	2007-10-17 08:42:53 -07:00
timer_list.c	…
timer_stats.c	…