This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug malloc/2186] ptmalloc mallopt(M_MMAP_MAX,) issue
- From: "neleai at seznam dot cz" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 16 Oct 2013 17:11:29 +0000
- Subject: [Bug malloc/2186] ptmalloc mallopt(M_MMAP_MAX,) issue
- Auto-submitted: auto-generated
- References: <bug-2186-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=2186
Ondrej Bilka <neleai at seznam dot cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
CC| |neleai at seznam dot cz
Resolution|--- |INVALID
--- Comment #1 from Ondrej Bilka <neleai at seznam dot cz> ---
If we would return null then we would cause programs fail even when there is
plenty of memory available.
I do not see any adverse effects of using mmap except of slower performance.
Unless you have an argument why should we avoid a mmap we will keep first
behavior.
--
You are receiving this mail because:
You are on the CC list for the bug.