From owner-freebsd-current@FreeBSD.ORG Wed Nov 30 22:48:10 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 0221716A420 for ; Wed, 30 Nov 2005 22:48:10 +0000 (GMT) (envelope-from jasone@canonware.com) Received: from lh.synack.net (lh.synack.net [204.152.188.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD27C43D7C for ; Wed, 30 Nov 2005 22:48:05 +0000 (GMT) (envelope-from jasone@canonware.com) Received: by lh.synack.net (Postfix, from userid 100) id 2638E5E48F5; Wed, 30 Nov 2005 14:48:05 -0800 (PST) Received: from [192.168.168.203] (moscow-cuda-gen2-68-64-60-20.losaca.adelphia.net [68.64.60.20]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by lh.synack.net (Postfix) with ESMTP id 8BAA15E48B0; Wed, 30 Nov 2005 14:48:02 -0800 (PST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <578B2B72-3092-4CE3-978B-84B1E3892F94@canonware.com> Content-Transfer-Encoding: 7bit From: Jason Evans Date: Wed, 30 Nov 2005 14:47:32 -0800 To: Claus Guttesen X-Mailer: Apple Mail (2.746.2) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on lh.synack.net X-Spam-Level: * X-Spam-Status: No, score=1.8 required=5.0 tests=RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 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: Wed, 30 Nov 2005 22:48:10 -0000 On Nov 30, 2005, at 1:02 AM, Claus Guttesen wrote: >> There is a patch that contains a new libc malloc implementation at: >> >> http://www.canonware.com/~jasone/jemalloc/jemalloc_20051127a.diff > > Do you need current for this? I patched and tried buildworld on 6.0 > stable but no go. I started work on this before 6.0 branched, and am unaware of any changes that would impact the patch. However, I've only used current for the development. Jason