diff options
| author | Jason Evans <jasone@canonware.com> | 2017-04-25 00:28:55 (GMT) |
|---|---|---|
| committer | Jason Evans <jasone@canonware.com> | 2017-04-25 03:37:16 (GMT) |
| commit | c67c3e4a63277718b9d137a38663c6ae324c99aa (patch) | |
| tree | 18d2f1f3a5eaaa0b5549c64691e6ed16c3c9f47c /INSTALL | |
| parent | e2cc6280ed96e2e6a2754d4e7187296e377d9548 (diff) | |
| download | jemalloc-c67c3e4a63277718b9d137a38663c6ae324c99aa.zip jemalloc-c67c3e4a63277718b9d137a38663c6ae324c99aa.tar.gz jemalloc-c67c3e4a63277718b9d137a38663c6ae324c99aa.tar.bz2 | |
Replace --disable-munmap with opt.munmap.
Control use of munmap(2) via a run-time option rather than a
compile-time option (with the same per platform default). The old
behavior of --disable-munmap can be achieved with
--with-malloc-conf=munmap:false.
This partially resolves #580.
Diffstat (limited to 'INSTALL')
| -rw-r--r-- | INSTALL | 9 |
1 files changed, 0 insertions, 9 deletions
@@ -128,15 +128,6 @@ any of the following arguments (not a definitive list) to 'configure': Statically link against the specified libunwind.a rather than dynamically linking with -lunwind. ---disable-munmap - Disable virtual memory deallocation via munmap(2); instead keep track of - the virtual memory for later use. munmap() is disabled by default (i.e. - --disable-munmap is implied) on [64-bit] Linux, which has a quirk in its - virtual memory allocation algorithm that causes semi-permanent VM map holes - under normal jemalloc operation. Although munmap() causes issues on 32-bit - Linux as well, it is not disabled by default due to the practical - possibility of address space exhaustion. - --disable-fill Disable support for junk/zero filling of memory. See the "opt.junk" and "opt.zero" option documentation for usage details. |