From owner-freebsd-current@FreeBSD.ORG Fri Jan 4 09:33:02 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17D0A16A418; Fri, 4 Jan 2008 09:33:02 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id C619713C45B; Fri, 4 Jan 2008 09:33:01 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 971C020BC; Fri, 4 Jan 2008 10:32:53 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 891F020A0; Fri, 4 Jan 2008 10:32:53 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 4B36B844CD; Fri, 4 Jan 2008 10:32:53 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Robert Watson References: <477C82F0.5060809@freebsd.org> <863ateemw2.fsf@ds4.des.no> <20080104002002.L30578@fledge.watson.org> Date: Fri, 04 Jan 2008 10:32:53 +0100 In-Reply-To: <20080104002002.L30578@fledge.watson.org> (Robert Watson's message of "Fri\, 4 Jan 2008 00\:26\:31 +0000 \(GMT\)") Message-ID: <86wsqqaqbe.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Jason Evans , Poul-Henning Kamp Subject: Re: sbrk(2) broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2008 09:33:02 -0000 Robert Watson writes: > The right answer is presumably to introduce a new LIMIT_SWAP, which > limits the allocation of anonymous memory by processes, and size it to > something like 90% of swap space by default. Not a good solution on its own. You need a per-process limit as well, otherwise a malloc() bomb will still cause other processes to fail randomly. > Since that won't be happening before 7.0, I believe the consensus is > to simply not MFC the changes for 7 and proceed with the release. Thank you :) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no