On Thu, 17 Mar 2011, Andrew Morton wrote: > commit 8bc719d3cab8414938f9ea6e33b58d8810d18068 > Author: Martin Schwidefsky <schwidefsky@xxxxxxxxxx> > AuthorDate: Mon Sep 25 23:31:20 2006 -0700 > Commit: Linus Torvalds <torvalds@xxxxxxxxxxx> > CommitDate: Tue Sep 26 08:48:47 2006 -0700 > > [PATCH] out of memory notifier > > Add a notifer chain to the out of memory killer. If one of the registered > callbacks could release some memory, do not kill the process but return and > retry the allocation that forced the oom killer to run. > > The purpose of the notifier is to add a safety net in the presence of > memory ballooners. If the resource manager inflated the balloon to a size > where memory allocations can not be satisfied anymore, it is better to > deflate the balloon a bit instead of killing processes. > > The implementation for the s390 ballooner is included. > I think it would be safe to do this only for CONSTRAINT_NONE in out_of_memory() since it's definitely not the right thing to do when a cpuset or mempolicy is oom; there's no guarantee that the freed memory is allocatable by the oom task. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>