Date: Fri, 22 May 2009 08:54:21 +0200 From: Jonathan McKeown <j.mckeown@ru.ac.za> To: freebsd-hackers@freebsd.org Subject: Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls? Message-ID: <200905220854.21917.j.mckeown@ru.ac.za> In-Reply-To: <Pine.GSO.4.64.0905211344370.1483@zeno.ucsd.edu> References: <4A14F58F.8000801@rawbw.com> <4A1594DA.2010707@rawbw.com> <Pine.GSO.4.64.0905211344370.1483@zeno.ucsd.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 21 May 2009 23:37:20 Nate Eldredge wrote: > Of course all these problems are solved, under any policy, by having more > memory or swap. =A0But overcommit allows you to do more with less. Or to put it another way, 90% of the problems that could be solved by havin= g=20 more memory can also be solved by pretending you have more memory and hopin= g=20 no-one calls your bluff. Jonathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905220854.21917.j.mckeown>