Date: 19 Jul 1999 18:39:15 +0200 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: "Kelly Yancey" <kbyanc@alcnet.com> Cc: "Dag-Erling Smorgrav" <des@flood.ping.uio.no>, <freebsd-hackers@freebsd.org> Subject: Re: Overcommit and calloc() Message-ID: <xzpyagclhl8.fsf@flood.ping.uio.no> In-Reply-To: "Kelly Yancey"'s message of "Mon, 19 Jul 1999 12:44:03 -0400" References: <001f01bed205$e8aeecc0$291c453f@kbyanc.alcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Kelly Yancey" <kbyanc@alcnet.com> writes: > Ahh...but wouldn't the bzero() touch all of the memory just allocated > functionally making it non-overcommit? No. If it were an "non-overcomitting malloc", it would return NULL and set errno to ENOMEM, instead of dumping core. 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?xzpyagclhl8.fsf>