This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Are M_ARENA_MAX and M_ARENA_TEST public mallopt parameters?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Cc: Siddhesh Poyarekar <siddhesh at redhat dot com>, Roland McGrath <roland at hack dot frob dot com>
- Date: Thu, 14 Mar 2013 15:08:03 -0400
- Subject: Are M_ARENA_MAX and M_ARENA_TEST public mallopt parameters?
Community,
In BZ#11261 [1] Ulrich says that M_ARENA_MAX and M_ARENA_TEST
are solutions to the problems surrounding highly threaded
applications running out of RAM with lots of arenas.
In malloc/malloc.c I see:
#ifdef PER_THREAD
/* Non public mallopt parameters. */
#define M_ARENA_TEST -7
#define M_ARENA_MAX -8
#endif
Yet in malloc/malloc.h I see:
/* mallopt options that actually do something */
#define M_TRIM_THRESHOLD -1
#define M_TOP_PAD -2
#define M_MMAP_THRESHOLD -3
#define M_MMAP_MAX -4
#define M_CHECK_ACTION -5
#define M_PERTURB -6
#define M_ARENA_TEST -7
#define M_ARENA_MAX -8
So which is it? Public? Private?
Do we document M_ARENA_TEST and M_ARENA_MAX and make them
work as expected?
Cheers,
Carlos.
[1] http://sourceware.org/bugzilla/show_bug.cgi?id=11261