Date: Sat, 05 Jan 2008 02:26:53 +0600 From: "Vadim Goncharov" <vadimnuclight@tpu.ru> To: "Peter Jeremy" <peterjeremy@optushome.com.au> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: sbrk(2), OOM-killer and malloc() overcommit Message-ID: <opt4e9q3n14fjv08@nuclight.avtf.net> In-Reply-To: <20080104192820.GM947@server.vk2pj.dyndns.org> References: <opt4euzyj44fjv08@nuclight.avtf.net> <20080104192820.GM947@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
05.01.08 @ 01:28 Peter Jeremy wrote: >> will make a bad reputation for FreeBSD as a server platform. But there >> are >> related "bug", in that of malloc overcommit, which can be demonstrated >> by >> this short program (if no resource limits are present, you'll see): > > This is a feature, not a bug. > >> http://people.freebsd.org/~kib/overcommit/index.html - but it has never >> gone into src tree. So why we still have this problem, why not have at >> least this patch?.. > > Overcommit has been bikeshedded extensively in the past. I suggest you > study the archives first. So why we are losing users due to this "feature", as other OSes provide tunables? Can I find somewhere summary of that discussions in archives? -- WBR, Vadim Goncharov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?opt4e9q3n14fjv08>