From owner-freebsd-chat Wed Apr 14 17:25:46 1999 Delivered-To: freebsd-chat@freebsd.org Received: from mail.webmaster.com (mail.webmaster.com [209.133.28.138]) by hub.freebsd.org (Postfix) with ESMTP id 2267815329 for ; Wed, 14 Apr 1999 17:25:32 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by mail.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Wed, 14 Apr 1999 17:14:21 -0700 From: "David Schwartz" To: , Cc: Subject: RE: swap-related problems Date: Wed, 14 Apr 1999 17:23:10 -0700 Message-ID: <000201be86d6$2464ed30$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <14101.8602.996328.135470@avalon.east> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I think Andrew Reilly's suggestion of having malloc > mmap it's own store file pretty well moots this disagreement. > I can scarcely believe I didn't think of it in the first place. You are assuming that malloc is the only overcommit case. I do not believe this is true. I believe that fork can cause an overcommit too. Likewise, even simply running multiple copies of the same executable causes an overcommit case. This may solve something, but it's not the general overcommit problem. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message