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

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Vadim Goncharov <vadimnuclight@...>
Cc: freebsd-current@freebsd.org <freebsd-current@...>
Date: Friday, January 4, 2008 - 3:28 pm

On Fri, Jan 04, 2008 at 09:08:12PM +0600, Vadim Goncharov wrote:
e=20
=20

This is a feature, not a bug.


Overcommit has been bikeshedded extensively in the past.  I suggest you
study the archives first.

--=20
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
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)