From owner-freebsd-chat Wed Apr 14 23: 9: 7 1999 Delivered-To: freebsd-chat@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.25]) by hub.freebsd.org (Postfix) with ESMTP id 57FAC14F06 for ; Wed, 14 Apr 1999 23:09:02 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id BAA27293; Thu, 15 Apr 1999 01:05:58 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 15 Apr 1999 01:05:57 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: davids@webmaster.com Cc: chat@FreeBSD.ORG Subject: RE: swap-related problems References: <14101.21892.460225.807747@avalon.east> <000001be86f8$fcd4d2d0$021d85d1@whenever.youwant.to> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14101.32737.825891.700729@avalon.east> Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoth David Schwartz on Wed, 14 April: : : I'm not sure I'm following you. How are you suggesting a person write a : portable application so that copy-on-write of its code or libraries doesn't : cause it to blow up in an overcommit situation? I'm not -- but at least the parent of a child that dies in this way can detect it. And it won't die because of an operation which the ANSI C standard specifies should be legal and return null was performed, if mmap-backed malloc is used. Which is an improvement. Your comments point out that the issue is much more grey than my earlier postings have painted it: A reliable malloc is insufficient to prevent over-commit death. Okay, so it's not good enough, practically. Let's do better: How about an mmap-backed fork? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message