From owner-freebsd-current@FreeBSD.ORG  Mon Dec 12 00:49:32 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by hub.freebsd.org (Postfix) with ESMTP id ABFC816A420;
	Mon, 12 Dec 2005 00:49:31 +0000 (GMT)
	(envelope-from davidxu@freebsd.org)
Message-ID: <439CC939.5080703@freebsd.org>
Date: Mon, 12 Dec 2005 08:50:01 +0800
From: David Xu <davidxu@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.7.10) Gecko/20050806
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Julian Elischer <julian@elischer.org>
References: <B6653214-2181-4342-854D-323979D23EE8@canonware.com>	<Pine.LNX.4.53.0511291121360.27754@regurgitate.ugcs.caltech.edu>	<0B746373-8C29-4ADF-9218-311AE08F3834@canonware.com>	<b41c75520512031245q48521143m@mail.gmail.com>	<7318D807-9086-4817-A40B-50D6960880FB@canonware.com>	<b41c75520512040451t360eb01u@mail.gmail.com>	<12CA5E15-D006-441D-A24C-1BCD1A69D740@canonware.com>
	<439CC5DA.3080103@elischer.org>
In-Reply-To: <439CC5DA.3080103@elischer.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Claus Guttesen <kometen@gmail.com>, Jason Evans <jasone@canonware.com>,
	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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2005 00:49:32 -0000

Julian Elischer wrote:

>>
>> No new problems in the malloc code have been found for some time  
>> now.  It has been tested on i386, sparc64, arm, and amd64.  In my  
>> opinion, the malloc patch is ready to be committed.  I am now 
>> working  on the assumption that new problems are more likely 
>> application bugs  than malloc bugs.  This seems like a good time to 
>> start sharing the  debugging load with the community. =)
>>
>> So, how about it?  Can this patch go in now?
>
>
>
> I may have missed it but some benchmark numbers could be good.
>
> Is there no way to make it an option for a while?
> that would get good testing AND a fallback for people.
>
I also would like to see any benchmark number, in fact, I had plan
to import ptmalloc in the past, the malloc problem had been discussed
several times in thread@ list.
Also, it would be nice if a fallback can be provided  :-)

David Xu