From owner-freebsd-hackers Sun Jul 11 18:47:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id BCF8214E3F for ; Sun, 11 Jul 1999 18:47:19 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id DAA32255; Mon, 12 Jul 1999 03:47:00 +0200 (CEST) (envelope-from des) To: Jon Ribbens Cc: "Daniel C. Sobral" , freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org, tech@openbsd.org Subject: Re: Replacement for grep(1) (part 2) References: <5laet8b2l8.fsf@assaris.sics.se> <5lemij265u.fsf@assaris.sics.se> <3788714D.4E666FFA@newsguy.com> <19990712002043.C7067@oaktree.co.uk> From: Dag-Erling Smorgrav Date: 12 Jul 1999 03:46:59 +0200 In-Reply-To: Jon Ribbens's message of "Mon, 12 Jul 1999 00:20:43 +0100" Message-ID: Lines: 17 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jon Ribbens writes: > "Daniel C. Sobral" 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