From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 9B487198005 for ; Tue, 26 Feb 2013 22:08:36 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4D037E0700; Tue, 26 Feb 2013 22:08:33 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6D2A4E06CC for ; Tue, 26 Feb 2013 22:08:32 +0000 (UTC) Received: from mail-gh0-f175.google.com (mail-gh0-f175.google.com [209.85.160.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mattst88) by smtp.gentoo.org (Postfix) with ESMTPSA id 8A12133DE10 for ; Tue, 26 Feb 2013 22:08:31 +0000 (UTC) Received: by mail-gh0-f175.google.com with SMTP id g18so793904ghb.20 for ; Tue, 26 Feb 2013 14:08:29 -0800 (PST) X-Received: by 10.236.148.164 with SMTP id v24mr24854817yhj.116.1361916509868; Tue, 26 Feb 2013 14:08:29 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.100.59.14 with HTTP; Tue, 26 Feb 2013 14:08:09 -0800 (PST) In-Reply-To: <3392533.WNcSa2bQvd@lebrodyl> References: <512CB9B8.9060308@gentoo.org> <3392533.WNcSa2bQvd@lebrodyl> From: Matt Turner Date: Tue, 26 Feb 2013 14:08:09 -0800 Message-ID: Subject: Re: [gentoo-dev] Evaluating a new malloc() To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 5af4b495-cc17-4eed-9399-902204ffbb86 X-Archives-Hash: edecddcd8a441202b1e819f1c4f2d348 On Tue, Feb 26, 2013 at 1:37 PM, Maciej Mrozowski wrote: > On Tuesday 26 of February 2013 11:44:31 Rich Freeman wrote: >> On Tue, Feb 26, 2013 at 11:35 AM, Alec Warner wrote: >> > I see a *HUGE* reason. glibc ships with ptmalloc. If you think they >> > should use jemalloc, talk to them. Don't just do it in Gentoo. >> >> Certainly I think it would be far more productive to talk to the glibc >> maintainers first. > > You mean productive like below? ;) > > http://sourceware.org/bugzilla/show_bug.cgi?id=11261 > > Ulrich Drepper: > "Stop reopening. There is a solution for people who are stupid enough to > create too many threads. No implementation will be perfect for everyone. The > glibc implementation is tuned for reasonable programs and will run much faster > than any other I tested." Drepper is no longer around. Upstream glibc is really friendly now, probably in an attempt to throw off the image you rightly had. > Merge of jemalloc upstream is likely never going to happen. Indeed, but not because of Drepper, but rather because GNU projects require copyright assignment for non-trivial contributions and I highly doubt that the jemalloc developers who put it under the BSD license are going to be okay with relicensing to LGPLv3+ and assigning copyright on their work to the FSF.