summaryrefslogtreecommitdiffstats
path: root/mm/oom_kill.c
diff options
context:
space:
mode:
authorDavid Rientjes <rientjes@google.com>2007-10-17 08:25:56 +0200
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-10-17 17:42:45 +0200
commitff0ceb9deb6eb017f52900b708d49cfa77bf25fb (patch)
treeaa33fef12afb05cb2644e7ae38b79ef6dd8ba59d /mm/oom_kill.c
parentoom: add per-zone locking (diff)
downloadlinux-ff0ceb9deb6eb017f52900b708d49cfa77bf25fb.tar.xz
linux-ff0ceb9deb6eb017f52900b708d49cfa77bf25fb.zip
oom: serialize out of memory calls
A final allocation attempt with a very high watermark needs to be attempted before invoking out_of_memory(). OOM killer serialization needs to occur before this final attempt, otherwise tasks attempting to OOM-lock all zones in its zonelist may spin and acquire the lock unnecessarily after the OOM condition has already been alleviated. If the final allocation does succeed, the zonelist is simply OOM-unlocked and __alloc_pages() returns the page. Otherwise, the OOM killer is invoked. If the task cannot acquire OOM-locks on all zones in its zonelist, it is put to sleep and the allocation is retried when it gets rescheduled. One of its zones is already marked as being in the OOM killer so it'll hopefully be getting some free memory soon, at least enough to satisfy a high watermark allocation attempt. This prevents needlessly killing a task when the OOM condition would have already been alleviated if it had simply been given enough time. Cc: Andrea Arcangeli <andrea@suse.de> Acked-by: Christoph Lameter <clameter@sgi.com> Signed-off-by: David Rientjes <rientjes@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/oom_kill.c')
0 files changed, 0 insertions, 0 deletions