> What you want is a combination of the two: a process turns off overallocation for itself,
and in exchange, is made immune to the OOM Killer.
I don't see the connection between these. Turning off overallocation just means that you get
a different error handling API. It certainly doesn't stop you from running the system out of
Making a process immune from the OOM killer is clearly a root-level operation; all you have to
do to force allocation is to touch pages after you allocate them, obviously not a root level
sort of ability.