Date: Thu, 24 Jul 2003 01:00:34 +0200 From: Matthias Buelow <mkb@mukappabeta.de> To: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory Message-ID: <20030723230034.GB24008@moghedien.mukappabeta.net> In-Reply-To: <20030723224436.GD22166@Odin.AC.HMC.Edu> References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> <20030723221336.GA26555@pit.databus.com> <20030723223654.GA24008@moghedien.mukappabeta.net> <20030723224436.GD22166@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis writes:
>No there isn't. Overcommit is a fundamental design feature of the BSD
>VM. If you don't like it, find an OS that doesn't do it. The only one
>I can think of off the top of my head in Irix where I've found it to be
>a serious pain in the ass.
Hmm, I could've sworn that fbsd's got some option to toggle it.
But apparently this is not so, a pity. I'd like to have the choice
between better resource usage (with overcommit enabled) and safer
operation (disabled, when an application won't crash at some random
point because it cannot get mapped memory).
--
Matthias Buelow; mkb@{mukappabeta.de,informatik.uni-wuerzburg.de}
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030723230034.GB24008>