public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tom at atoptech dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11044] malloc dynamic mmap threshold causes 50%-100% increase in memory usage
Date: Mon, 05 Apr 2010 16:10:00 -0000 [thread overview]
Message-ID: <20100405161002.20885.qmail@sourceware.org> (raw)
In-Reply-To: <20091202183137.11044.tom@atoptech.com>
------- Additional Comments From tom at atoptech dot com 2010-04-05 16:10 -------
Ulrich,
> No malloc can work perfectly in all situations....
That is the point. This change had no statistical basis proving that it improved
the malloc behavior on average (at least I'm not aware of any papers on the
subject).
> Aside, you are not reporting anything about current releases.
Correct me in I'm wrong, but this change is in the current release.
Regards,
Tom Geocaris
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11044
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-04-05 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 18:31 [Bug libc/11044] New: " tom at atoptech dot com
2010-04-05 5:08 ` [Bug libc/11044] " drepper at redhat dot com
2010-04-05 16:10 ` tom at atoptech dot com [this message]
2010-04-05 18:32 ` drepper at redhat dot com
2010-04-05 18:35 ` drepper at redhat dot com
2010-04-07 17:09 ` tom at atoptech dot com
[not found] <bug-11044-131@http.sourceware.org/bugzilla/>
2014-02-16 17:43 ` jackie.rosen at hushmail dot com
2014-05-28 19:46 ` schwab at sourceware dot org
2014-06-30 20:35 ` fweimer at redhat dot com
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=20100405161002.20885.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).