Gentoo Archives: gentoo-dev

From: Matt Turner <mattst88@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Evaluating a new malloc()
Date: Tue, 26 Feb 2013 22:08:36
Message-Id: CAEdQ38FykUEV7D5AqJpSP5Wtaa8-1TziZ9XS3+K7F0BcnY_X=g@mail.gmail.com
In Reply to: Re: [gentoo-dev] Evaluating a new malloc() by Maciej Mrozowski
1 On Tue, Feb 26, 2013 at 1:37 PM, Maciej Mrozowski <reavertm@×××××.com> wrote:
2 > On Tuesday 26 of February 2013 11:44:31 Rich Freeman wrote:
3 >> On Tue, Feb 26, 2013 at 11:35 AM, Alec Warner <antarus@g.o> wrote:
4 >> > I see a *HUGE* reason. glibc ships with ptmalloc. If you think they
5 >> > should use jemalloc, talk to them. Don't just do it in Gentoo.
6 >>
7 >> Certainly I think it would be far more productive to talk to the glibc
8 >> maintainers first.
9 >
10 > You mean productive like below? ;)
11 >
12 > http://sourceware.org/bugzilla/show_bug.cgi?id=11261
13 >
14 > Ulrich Drepper:
15 > "Stop reopening. There is a solution for people who are stupid enough to
16 > create too many threads. No implementation will be perfect for everyone. The
17 > glibc implementation is tuned for reasonable programs and will run much faster
18 > than any other I tested."
19
20 Drepper is no longer around. Upstream glibc is really friendly now,
21 probably in an attempt to throw off the image you rightly had.
22
23 > Merge of jemalloc upstream is likely never going to happen.
24
25 Indeed, but not because of Drepper, but rather because GNU projects
26 require copyright assignment for non-trivial contributions and I
27 highly doubt that the jemalloc developers who put it under the BSD
28 license are going to be okay with relicensing to LGPLv3+ and assigning
29 copyright on their work to the FSF.