From: Maciej Mrozowski <reavertm@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Evaluating a new malloc()
Date: Tue, 26 Feb 2013 22:37:42 +0100 [thread overview]
Message-ID: <3392533.WNcSa2bQvd@lebrodyl> (raw)
In-Reply-To: <CAGfcS_=uPcTVWuk2n8WFiHk1d0q3Bm+cf6f5tO3FNmwQy2MK6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
On Tuesday 26 of February 2013 11:44:31 Rich Freeman wrote:
> On Tue, Feb 26, 2013 at 11:35 AM, Alec Warner <antarus@gentoo.org> 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."
Merge of jemalloc upstream is likely never going to happen.
regards
MM
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-02-26 21:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 13:33 [gentoo-dev] Evaluating a new malloc() Richard Yao
2013-02-26 13:35 ` Diego Elio Pettenò
2013-02-26 13:46 ` Richard Yao
2013-02-26 13:48 ` Alexander Berntsen
2013-02-26 13:52 ` Richard Yao
2013-02-26 14:25 ` Florian Philipp
2013-02-26 16:35 ` Alec Warner
2013-02-26 16:44 ` Rich Freeman
2013-02-26 21:37 ` Maciej Mrozowski [this message]
2013-02-26 21:49 ` Jeff Horelick
2013-02-26 22:08 ` Matt Turner
2013-03-19 21:08 ` Mike Frysinger
2013-02-26 19:10 ` Matt Turner
2013-02-27 0:07 ` William Hubbs
2013-02-26 16:40 ` Mike Gilbert
2013-02-27 5:22 ` [gentoo-dev] " Ryan Hill
2013-02-27 16:15 ` Peter Stuge
2013-02-27 20:26 ` [gentoo-dev] " Sergei Trofimovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3392533.WNcSa2bQvd@lebrodyl \
--to=reavertm@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox