From owner-freebsd-current@FreeBSD.ORG Thu Jan 3 19:21:09 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 7FEB816A46E; Thu, 3 Jan 2008 19:21:09 +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 3404C13C442; Thu, 3 Jan 2008 19:21:09 +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 AC6D52089; Thu, 3 Jan 2008 20:21:01 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.1/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 9D83C207E; Thu, 3 Jan 2008 20:21:01 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 80C838449F; Thu, 3 Jan 2008 20:21:01 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jason Evans References: <477C82F0.5060809@freebsd.org> Date: Thu, 03 Jan 2008 20:21:01 +0100 In-Reply-To: <477C82F0.5060809@freebsd.org> (Jason Evans's message of "Wed\, 02 Jan 2008 22\:38\:40 -0800") Message-ID: <863ateemw2.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, 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: Thu, 03 Jan 2008 19:21:09 -0000 Jason Evans writes: > [sbrk is broken] The real question is why we would revert perfectly good code (jemalloc) from using a modern interface to using one that has been obsolete for twenty years, and marked as such in the man page for seven years. If rwatson@ wants malloc() to respect resource limits, he can bloody well fix mmap(). Until he does, the datasize limit is a joke anyway, as anyone can circumvent it by either using mmap() instead of malloc() or setting _malloc_options before calling malloc(). DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no