summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorJason Evans <je@fb.com>2012-03-17 00:09:32 (GMT)
committerJason Evans <je@fb.com>2012-03-17 00:09:32 (GMT)
commite7b8fa18d256e0bc18b61ee03b69af87fa3d7969 (patch)
treef947c833c23dcf7ecac04b4234c52f6f7a8200b4 /doc
parent39006f990771518b1b7d4b8dfdfac72409ef26ca (diff)
downloadjemalloc-e7b8fa18d256e0bc18b61ee03b69af87fa3d7969.zip
jemalloc-e7b8fa18d256e0bc18b61ee03b69af87fa3d7969.tar.gz
jemalloc-e7b8fa18d256e0bc18b61ee03b69af87fa3d7969.tar.bz2
Rename the "tcache.flush" mallctl to "thread.tcache.flush".
Diffstat (limited to 'doc')
-rw-r--r--doc/jemalloc.xml.in36
1 files changed, 18 insertions, 18 deletions
diff --git a/doc/jemalloc.xml.in b/doc/jemalloc.xml.in
index 926deaf..ffc6c94 100644
--- a/doc/jemalloc.xml.in
+++ b/doc/jemalloc.xml.in
@@ -1032,24 +1032,6 @@ malloc_conf = "xmalloc:true";]]></programlisting>
<varlistentry>
<term>
- <mallctl>tcache.flush</mallctl>
- (<type>void</type>)
- <literal>--</literal>
- [<option>--enable-tcache</option>]
- </term>
- <listitem><para>Flush calling thread's tcache. This interface releases
- all cached objects and internal data structures associated with the
- calling thread's thread-specific cache. Ordinarily, this interface
- need not be called, since automatic periodic incremental garbage
- collection occurs, and the thread cache is automatically discarded when
- a thread exits. However, garbage collection is triggered by allocation
- activity, so it is possible for a thread that stops
- allocating/deallocating to retain its cache indefinitely, in which case
- the developer may find manual flushing useful.</para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
<mallctl>thread.arena</mallctl>
(<type>unsigned</type>)
<literal>rw</literal>
@@ -1119,6 +1101,24 @@ malloc_conf = "xmalloc:true";]]></programlisting>
<function>mallctl*<parameter/></function> calls.</para></listitem>
</varlistentry>
+ <varlistentry>
+ <term>
+ <mallctl>thread.tcache.flush</mallctl>
+ (<type>void</type>)
+ <literal>--</literal>
+ [<option>--enable-tcache</option>]
+ </term>
+ <listitem><para>Flush calling thread's tcache. This interface releases
+ all cached objects and internal data structures associated with the
+ calling thread's thread-specific cache. Ordinarily, this interface
+ need not be called, since automatic periodic incremental garbage
+ collection occurs, and the thread cache is automatically discarded when
+ a thread exits. However, garbage collection is triggered by allocation
+ activity, so it is possible for a thread that stops
+ allocating/deallocating to retain its cache indefinitely, in which case
+ the developer may find manual flushing useful.</para></listitem>
+ </varlistentry>
+
<varlistentry id="arenas.narenas">
<term>
<mallctl>arenas.narenas</mallctl>