From owner-freebsd-current@FreeBSD.ORG Mon Dec 12 00:35:42 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 83F4E16A41F for ; Mon, 12 Dec 2005 00:35:42 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3093943D55 for ; Mon, 12 Dec 2005 00:35:42 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [192.168.2.6]) ([10.251.60.53]) by a50.ironport.com with ESMTP; 11 Dec 2005 16:35:39 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <439CC5DA.3080103@elischer.org> Date: Sun, 11 Dec 2005 16:35:38 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jason Evans References: <0B746373-8C29-4ADF-9218-311AE08F3834@canonware.com> <7318D807-9086-4817-A40B-50D6960880FB@canonware.com> <12CA5E15-D006-441D-A24C-1BCD1A69D740@canonware.com> In-Reply-To: <12CA5E15-D006-441D-A24C-1BCD1A69D740@canonware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org, Claus Guttesen 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 00:35:42 -0000 Jason Evans wrote: > On Dec 4, 2005, at 4:51 AM, Claus Guttesen wrote: > >> I was able to do a buildworld on current with this patch, but I had >> problems getting X to run and kldxref took all my space on the >> root-partition doing a installkernel. > > > I've fixed the offending bug in kldxref in the latest patch: > > http://www.canonware.com/~jasone/jemalloc/jemalloc_20051211b.diff > > I spent several hours poking at X, but was never able to determine > why it goes into an infinite loop. The infinite loop happens rather > early, during the load of the libbitmap module. My best guess is > that it is stuck trying to acquire the Xlib lock, but cannot be sure, > since I don't know how to get debug symbols for the loaded X module. > In any case, malloc is nowhere in the backtrace. I do not have the > time to acquire the X expertise that is likely needed to track down > this problem. Hopefully someone else will be willing to do so. > > 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. > > Thanks, > Jason > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org"