public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mtk.manpages at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12129] mallopt() M_MXFAST limit anomaly
Date: Sun, 24 Oct 2010 07:56:00 -0000 [thread overview]
Message-ID: <20101024075600.7SJ34Up0JixlEiFAUj596wu2VHSu4ao6_cixiU-VoPE@z> (raw)
In-Reply-To: <bug-12129-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12129
Michael Kerrisk <mtk.manpages at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|mallop() M_MXFAST limit |mallopt() M_MXFAST limit
|anomaly |anomaly
--- Comment #2 from Michael Kerrisk <mtk.manpages at gmail dot com> 2010-10-24 05:26:31 UTC ---
(In reply to comment #1)
> The interface is what it is. Any change can only cause problems.
This makes no sense. What possible problems can arise from a correct fix?
This interface is purely about performance. A correct fix will only have the
effect of changing the performance characteristics of some programs. Leaving
this interface in the current broken state means that some programs will not
obtain the performance improvement they expect from using the interface.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2010-10-24 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 14:33 [Bug libc/12129] New: mallop() " mtk.manpages at gmail dot com
2010-10-17 15:14 ` [Bug libc/12129] " drepper.fsp at gmail dot com
2010-10-24 7:56 ` mtk.manpages at gmail dot com [this message]
2011-01-26 0:55 ` [Bug libc/12129] mallopt() " LpSolit at netscape dot net
2012-03-29 4:39 ` mtk.manpages at gmail dot com
2013-03-17 17:31 ` carlos at redhat dot com
2013-04-15 9:35 ` [Bug malloc/12129] " siddhesh at redhat dot com
2014-06-30 7:48 ` fweimer at redhat dot com
2021-06-30 17:01 ` maxkamper at outlook 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=20101024075600.7SJ34Up0JixlEiFAUj596wu2VHSu4ao6_cixiU-VoPE@z \
--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).