Date: Sat, 05 Jan 2008 00:32:04 +0600 From: "Vadim Goncharov" <vadimnuclight@tpu.ru> To: "Tim Kientzle" <kientzle@freebsd.org> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: sbrk(2), OOM-killer and malloc() overcommit Message-ID: <opt4e4fqv34fjv08@nuclight.avtf.net> In-Reply-To: <477E6EB7.1010004@freebsd.org> References: <opt4euzyj44fjv08@nuclight.avtf.net> <477E6EB7.1010004@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
04.01.08 @ 23:36 Tim Kientzle wrote: > Vadim Goncharov wrote: >> ... related "bug", in that of malloc overcommit,... > > malloc overcommit is not a bug; it's an important > feature for many applications, for the same > reasons that sparse files are an important feature. > (Many applications can optimize performance by > using an addressable region much larger than the > actual data they need to store.) What applications? How do they use this "feature"? > If you really need a 4G block of memory, mmap() > it to a file on disk. That's not a solution for end-user. Why just not have space reserving, as other operating systems can guarantee to their applications that stable availability of memory? -- WBR, Vadim Goncharov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?opt4e4fqv34fjv08>