Skip site navigation (1)Skip section navigation (2)
Date:      12 Jul 1999 03:46:59 +0200
From:      Dag-Erling Smorgrav <des@flood.ping.uio.no>
To:        Jon Ribbens <jon@oaktree.co.uk>
Cc:        "Daniel C. Sobral" <dcs@newsguy.com>, freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org, tech@openbsd.org
Subject:   Re: Replacement for grep(1) (part 2)
Message-ID:  <xzpiu7qiqr0.fsf@flood.ping.uio.no>
In-Reply-To: Jon Ribbens's message of "Mon, 12 Jul 1999 00:20:43 %2B0100"
References:  <Pine.GSO.4.10.9907052110250.13873-100000@uther.wam.umd.edu> <xzp7locthir.fsf@flood.ping.uio.no> <xzp1zektgp2.fsf@flood.ping.uio.no> <5laet8b2l8.fsf@assaris.sics.se> <xzpiu7wrx7q.fsf@flood.ping.uio.no> <5lemij265u.fsf@assaris.sics.se> <3788714D.4E666FFA@newsguy.com> <19990712002043.C7067@oaktree.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
Jon Ribbens <jon@oaktree.co.uk> writes:
> "Daniel C. Sobral" <dcs@newsguy.com> wrote:
> > OTOH, though, FreeBSD's malloc() is very unlikely to return an out
> > of memory error.
> Why is that?

Because FreeBSD overcommits memory. You can allocate (almost) as much
memory as you want regardless of how much RAM / swap you have. You
won't run into trouble unless you actually try to use too much of it.

> What happens if the process hits its resource limits?

Malloc() fails with ENOMEM.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpiu7qiqr0.fsf>