public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "simberger at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/1128] Malloc not trimming filled-up sbrk space causes unnecessary system call overhead Date: Thu, 01 Oct 2009 12:20:00 -0000 [thread overview] Message-ID: <20091001121948.22055.qmail@sourceware.org> (raw) In-Reply-To: <20050727134634.1128.jp-www@dcs.gla.ac.uk> ------- Additional Comments From simberger at gmail dot com 2009-10-01 12:19 ------- oops, misinterpreted the topic of this bug: my previous test case is for the Problem 'Malloc trimming filled-up sbrk space too aggressively causes unnecessary system call overhead' It is still a serious problem (caused about 50% slow down in a real world program. The only possible work around was to introduce much more complicated memory management in my application) -- http://sourceware.org/bugzilla/show_bug.cgi?id=1128 ------- 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:[~2009-10-01 12:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-27 13:46 [Bug libc/1128] New: " jp-www at dcs dot gla dot ac dot uk 2008-03-28 5:55 ` [Bug libc/1128] " kkylheku at gmail dot com 2008-03-28 6:01 ` kkylheku at gmail dot com 2008-03-28 17:45 ` bugzilla1 at malloc dot de 2008-03-28 18:05 ` bugzilla1 at malloc dot de 2008-07-18 20:07 ` kkylheku at gmail dot com 2008-07-20 19:42 ` jp-www at dcs dot gla dot ac dot uk 2009-10-01 12:03 ` simberger at gmail dot com 2009-10-01 12:20 ` simberger at gmail dot com [this message] 2009-10-01 17:15 ` bugzilla1 at malloc dot de
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=20091001121948.22055.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: linkBe 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).