summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorQi Wang <interwq@gwu.edu>2019-07-25 20:43:59 (GMT)
committerQi Wang <interwq@gmail.com>2019-07-25 22:25:58 (GMT)
commit9f6a9f4c1f78fd61297e01ae1521af9696d2023b (patch)
tree8a9d51464cd879272acc283a6bdfe856a89b3a45
parent10fcff6c38c08bc2b1a672ff92701012944d843a (diff)
downloadjemalloc-9f6a9f4c1f78fd61297e01ae1521af9696d2023b.zip
jemalloc-9f6a9f4c1f78fd61297e01ae1521af9696d2023b.tar.gz
jemalloc-9f6a9f4c1f78fd61297e01ae1521af9696d2023b.tar.bz2
Update manual for opt.retain (new default on Windows).
-rw-r--r--doc/jemalloc.xml.in22
1 files changed, 11 insertions, 11 deletions
diff --git a/doc/jemalloc.xml.in b/doc/jemalloc.xml.in
index e23ccb7..7fecda7 100644
--- a/doc/jemalloc.xml.in
+++ b/doc/jemalloc.xml.in
@@ -963,17 +963,17 @@ mallctl("arena." STRINGIFY(MALLCTL_ARENAS_ALL) ".decay",
linkend="stats.retained">stats.retained</link> for related details).
It also makes jemalloc use <citerefentry>
<refentrytitle>mmap</refentrytitle><manvolnum>2</manvolnum>
- </citerefentry> in a more greedy way, mapping larger chunks in one go.
- This option is disabled by default unless discarding virtual memory is
- known to trigger
- platform-specific performance problems, e.g. for [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
- <citerefentry><refentrytitle>munmap</refentrytitle>
- <manvolnum>2</manvolnum></citerefentry> causes issues on 32-bit Linux as
- well, retaining virtual memory for 32-bit Linux is disabled by default
- due to the practical possibility of address space exhaustion.
- </para></listitem>
+ </citerefentry> or equivalent in a more greedy way, mapping larger
+ chunks in one go. This option is disabled by default unless discarding
+ virtual memory is known to trigger platform-specific performance
+ problems, namely 1) for [64-bit] Linux, which has a quirk in its virtual
+ memory allocation algorithm that causes semi-permanent VM map holes
+ under normal jemalloc operation; and 2) for [64-bit] Windows, which
+ disallows split / merged regions with
+ <parameter><constant>MEM_RELEASE</constant></parameter>. Although the
+ same issues may present on 32-bit platforms as well, retaining virtual
+ memory for 32-bit Linux and Windows is disabled by default due to the
+ practical possibility of address space exhaustion. </para></listitem>
</varlistentry>
<varlistentry id="opt.dss">