Home » Mailing list archives » freebsd-current » 2008 » January » 4

Re: sbrk(2), OOM-killer and malloc() overcommit

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Tim Kientzle <kientzle@...>
To: Vadim Goncharov <vadimnuclight@...>
Cc: freebsd-current@freebsd.org <freebsd-current@...>
Subject: Re: sbrk(2), OOM-killer and malloc() overcommit
Date: Friday, January 4, 2008 - 1:36 pm

Vadim Goncharov wrote:

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.)

If you really need a 4G block of memory, mmap()
it to a file on disk.

Tim Kientzle
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
sbrk(2), OOM-killer and malloc() overcommit, Vadim Goncharov, (Fri Jan 4, 11:08 am)
Re: sbrk(2), OOM-killer and malloc() overcommit, Peter Jeremy, (Fri Jan 4, 3:28 pm)
Re: sbrk(2), OOM-killer and malloc() overcommit, Vadim Goncharov, (Fri Jan 4, 4:26 pm)
Re: sbrk(2), OOM-killer and malloc() overcommit, Peter Jeremy, (Fri Jan 4, 9:10 pm)
Re: sbrk(2), OOM-killer and malloc() overcommit, Vadim Goncharov, (Sat Jan 5, 10:44 am)
Re: sbrk(2), OOM-killer and malloc() overcommit, Dag-Erling Smørgrav, (Mon Jan 7, 10:58 am)
Re: sbrk(2), OOM-killer and malloc() overcommit, Vadim Goncharov, (Mon Jan 7, 12:06 pm)
Re: sbrk(2), OOM-killer and malloc() overcommit, Tim Kientzle, (Fri Jan 4, 1:36 pm)
Re: sbrk(2), OOM-killer and malloc() overcommit, Vadim Goncharov, (Fri Jan 4, 2:32 pm)