linux/kernel
Linus Torvalds e80eda94d3 Posix timers: limit number of timers firing at once
Bursty timers aren't good for anybody, very much including latency for
other programs when we trigger lots of timers in interrupt context.  So
set a random limit, after which we'll handle the rest on the next timer
tick.

Noted by Oleg Nesterov <oleg@tv-sign.ru>

Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-23 10:02:50 -07:00
..
irq
power
acct.c
audit.c
auditsc.c
capability.c
compat.c
configs.c
cpu.c
cpuset.c
crash_dump.c
dma.c
exec_domain.c
exit.c [PATCH] Call exit_itimers from do_exit, not __exit_signal 2005-10-21 15:38:08 -07:00
extable.c
fork.c
futex.c
intermodule.c
itimer.c
kallsyms.c
Kconfig.hz
Kconfig.preempt
kexec.c
kfifo.c
kmod.c
kprobes.c
ksysfs.c
kthread.c
Makefile
module.c
panic.c
params.c
pid.c
posix-cpu-timers.c Posix timers: limit number of timers firing at once 2005-10-23 10:02:50 -07:00
posix-timers.c [PATCH] Call exit_itimers from do_exit, not __exit_signal 2005-10-21 15:38:08 -07:00
printk.c
profile.c
ptrace.c
rcupdate.c
resource.c
sched.c
seccomp.c
signal.c [PATCH] Call exit_itimers from do_exit, not __exit_signal 2005-10-21 15:38:08 -07:00
softirq.c
softlockup.c
spinlock.c
stop_machine.c
sys_ni.c
sys.c
sysctl.c
time.c
timer.c
uid16.c
user.c
wait.c
workqueue.c