This is the mail archive of the
mailing list for the glibc project.
Re: [PING] [v9] malloc: Consistently apply trim_threshold to all heaps [BZ #17195]
- From: Mel Gorman <mgorman at suse dot de>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: Siddhesh Poyarekar <siddhesh at redhat dot com>, Mike Frysinger <vapier at gentoo dot org>, Julian Taylor <jtaylor dot debian at googlemail dot com>, Chris Metcalf <cmetcalf at ezchip dot com>, libc-alpha at sourceware dot org
- Date: Tue, 24 Mar 2015 15:46:45 +0000
- Subject: Re: [PING] [v9] malloc: Consistently apply trim_threshold to all heaps [BZ #17195]
- Authentication-results: sourceware.org; auth=none
- References: <20150306142934 dot GX3087 at suse dot de> <20150316161333 dot GA3087 at suse dot de> <55071DB5 dot 5010702 at redhat dot com>
On Mon, Mar 16, 2015 at 02:15:17PM -0400, Carlos O'Donell wrote:
> On 03/16/2015 12:13 PM, Mel Gorman wrote:
> > On Fri, Mar 06, 2015 at 02:29:34PM +0000, Mel Gorman wrote:
> >> Trimming heaps is a balance between saving memory and the system overhead
> >> required to update page tables and discard allocated pages. The malloc
> >> option M_TRIM_THRESHOLD is a tunable that users are meant to use to decide
> >> where this balance point is but it is only applied to the main arena.
> > Ping as it's been a while since anyone said anything on it. I note it's
> > in patchwork (http://patchwork.sourceware.org/patch/5496/) but do not
> > know if that means anyone plans to look at it. Thanks.
> I actually have a build going with your patch and I'm trying to stress test
> it to see what impact it has on some real applications.
Thanks. Any luck with this?