summaryrefslogtreecommitdiffstats
path: root/arch/i386
diff options
context:
space:
mode:
authorChristoph Lameter <clameter@engr.sgi.com>2006-02-20 18:27:52 -0800
committerLinus Torvalds <torvalds@g5.osdl.org>2006-02-20 20:00:09 -0800
commit9b0f8b040acd8dfd23860754c0d09ff4f44e2cbc (patch)
tree33c69908705c88b86f14d9e835b6dee6a9c3a31b /arch/i386
parent9827b781f20828e5ceb911b879f268f78fe90815 (diff)
downloadop-kernel-dev-9b0f8b040acd8dfd23860754c0d09ff4f44e2cbc.zip
op-kernel-dev-9b0f8b040acd8dfd23860754c0d09ff4f44e2cbc.tar.gz
[PATCH] Terminate process that fails on a constrained allocation
Some allocations are restricted to a limited set of nodes (due to memory policies or cpuset constraints). If the page allocator is not able to find enough memory then that does not mean that overall system memory is low. In particular going postal and more or less randomly shooting at processes is not likely going to help the situation but may just lead to suicide (the whole system coming down). It is better to signal to the process that no memory exists given the constraints that the process (or the configuration of the process) has placed on the allocation behavior. The process may be killed but then the sysadmin or developer can investigate the situation. The solution is similar to what we do when running out of hugepages. This patch adds a check before we kill processes. At that point performance considerations do not matter much so we just scan the zonelist and reconstruct a list of nodes. If the list of nodes does not contain all online nodes then this is a constrained allocation and we should kill the current process. Signed-off-by: Christoph Lameter <clameter@sgi.com> Cc: Nick Piggin <nickpiggin@yahoo.com.au> Cc: Andi Kleen <ak@muc.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'arch/i386')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud