From owner-freebsd-current@FreeBSD.ORG Mon Dec 12 03:21:40 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B13316A41F for ; Mon, 12 Dec 2005 03:21:40 +0000 (GMT) (envelope-from bucht@acc.umu.se) Received: from mail.acc.umu.se (mail.acc.umu.se [130.239.18.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD63443D8D for ; Mon, 12 Dec 2005 03:21:32 +0000 (GMT) (envelope-from bucht@acc.umu.se) Received: from localhost (localhost [127.0.0.1]) by amavisd-new (Postfix) with ESMTP id 1CD01498A; Mon, 12 Dec 2005 04:21:32 +0100 (MET) Received: from [192.168.1.100] (53dbce07.umea.cust.skycom.se [83.219.206.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.acc.umu.se (Postfix) with ESMTP id 3484A4989; Mon, 12 Dec 2005 04:21:31 +0100 (MET) Message-ID: <439CED01.9050108@acc.umu.se> Date: Mon, 12 Dec 2005 04:22:41 +0100 From: Johan Bucht User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050616) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jason Evans References: <20051212014852.GA8775@shaka.acc.umu.se> <9FAD2B4B-C167-42D7-A8E7-BE03F4C07543@canonware.com> <439CEB74.9080505@acc.umu.se> In-Reply-To: <439CEB74.9080505@acc.umu.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at acc.umu.se Cc: current@freebsd.org Subject: Re: New libc malloc patch 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: Mon, 12 Dec 2005 03:21:40 -0000 Johan Bucht wrote: >>> * Fork safety functions >>> Nice to have for all allocators and is something I missed having. >>> Would >>> like to have them regardless if your malloc becomes standard or not. >> >> >> >> I think that the implementation is currently fork-safe. The threads >> libraries call _malloc_prefork() and _malloc_postfork() in order to >> avoid locking issues. >> > Hmm, I meant that the _malloc_prefork() functions are independent from > your malloc allocation and I would like them committed regardless as > they make the life easier for other malloc implementation. Bah, the libc bits not the actual functions of course. =) Should probably go to sleep instead of writing semi-understandable sentences. /Johan Bucht