linux/arch/um
Jeff Dike c83e448420 uml: an idle system should have zero load average
The ever-vigilant users of linode.com noticed that an idle 2.6 UML has a
persistent load average of ~.4.

It turns out that because the UML timer handler processed softirqs before
actually delivering the tick, the tick was counted in the context of the idle
thread about half the time.

Signed-off-by: Jeff Dike <jdike@linux.intel.com>
Cc: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-08 11:14:57 -07:00
..
drivers uml: rename os_{read_write}_file_k back to os_{read_write}_file 2007-05-07 12:13:03 -07:00
include uml: fix prototypes 2007-05-07 12:13:04 -07:00
kernel uml: an idle system should have zero load average 2007-05-08 11:14:57 -07:00
os-Linux uml: more page fault path trimming 2007-05-07 12:13:04 -07:00
scripts
sys-i386 uml: more page fault path trimming 2007-05-07 12:13:04 -07:00
sys-ia64
sys-ppc uml: remove user_util.h 2007-05-07 12:13:01 -07:00
sys-x86_64 uml: more page fault path trimming 2007-05-07 12:13:04 -07:00
Kconfig
Kconfig.char
Kconfig.debug
Kconfig.i386
Kconfig.net
Kconfig.scsi
Kconfig.x86_64
Makefile
Makefile-i386
Makefile-ia64
Makefile-os-Linux
Makefile-ppc
Makefile-skas
Makefile-tt
Makefile-x86_64
config.release
defconfig