From 5ae78de4e4f6e220e29ad2f54b95a0098da4b365 Mon Sep 17 00:00:00 2001
From: Hans Bolinder
Date: Mon, 12 Oct 2015 12:12:27 +0200
Subject: [erts] Correct documentation
Fix mistakes found by 'xmllint'.
---
erts/doc/src/erts_alloc.xml | 74 ++++++++++++++++++++++-----------------------
1 file changed, 37 insertions(+), 37 deletions(-)
(limited to 'erts/doc/src/erts_alloc.xml')
diff --git a/erts/doc/src/erts_alloc.xml b/erts/doc/src/erts_alloc.xml
index 376cae4a95..15b78ffa10 100644
--- a/erts/doc/src/erts_alloc.xml
+++ b/erts/doc/src/erts_alloc.xml
@@ -4,7 +4,7 @@
- acul |de]]>
+ acul |de]]>
-
Abandon carrier utilization limit. A valid
]]> is an integer in the range
@@ -422,7 +422,7 @@
allocators based on the alloc_util framework with the
exception of temp_alloc (which would be pointless).
- as bf|aobf|aoff|aoffcbf|aoffcaobf|gf|af]]>
+ as bf|aobf|aoff|aoffcbf|aoffcaobf|gf|af]]>
-
Allocation strategy. Valid strategies are bf (best fit),
aobf (address order best fit), aoff (address order first fit),
@@ -430,7 +430,7 @@
aoffcaobf (address order first fit carrier address order best fit),
gf (good fit), and af (a fit). See
the description of allocation strategies in "the alloc_util framework" section.
- asbcst ]]>
+ asbcst ]]>
-
Absolute singleblock carrier shrink threshold (in
kilobytes). When a block located in an
@@ -438,23 +438,23 @@
will be left unchanged if the amount of unused memory is less
than this threshold; otherwise, the carrier will be shrunk.
See also rsbcst.
- e true|false]]>
+ e true|false]]>
-
Enable allocator ]]>.
- lmbcs ]]>
+ lmbcs ]]>
-
Largest (mseg_alloc) multiblock carrier size (in
kilobytes). See the description
on how sizes for mseg_alloc multiblock carriers are decided
in "the alloc_util framework" section. On 32-bit Unix style OS
this limit can not be set higher than 128 megabyte.
- mbcgs ]]>
+ mbcgs ]]>
-
(mseg_alloc) multiblock carrier growth stages. See
the description on how sizes for
mseg_alloc multiblock carriers are decided
in "the alloc_util framework" section.
- mbsd ]]>
+ mbsd ]]>
-
Max block search depth. This flag has effect only if the
good fit strategy has been selected for allocator
@@ -464,40 +464,40 @@
search depth sets a limit on the maximum number of blocks to
inspect in a free list during a search for suitable block
satisfying the request.
- mmbcs ]]>
+ mmbcs ]]>
-
Main multiblock carrier size. Sets the size of the main
multiblock carrier for allocator ]]>. The main
multiblock carrier is allocated via and is
never deallocated.
- mmmbc ]]>
+ mmmbc ]]>
-
Max mseg_alloc multiblock carriers. Maximum number of
multiblock carriers allocated via mseg_alloc by
allocator ]]>. When this limit has been reached,
new multiblock carriers will be allocated via
sys_alloc.
- mmsbc ]]>
+ mmsbc ]]>
-
Max mseg_alloc singleblock carriers. Maximum number of
singleblock carriers allocated via mseg_alloc by
allocator ]]>. When this limit has been reached,
new singleblock carriers will be allocated via
sys_alloc.
- ramv ]]>
+ ramv ]]>
-
Realloc always moves. When enabled, reallocate operations will
more or less be translated into an allocate, copy, free sequence.
This often reduce memory fragmentation, but costs performance.
- rmbcmt ]]>
+ rmbcmt ]]>
-
Relative multiblock carrier move threshold (in percent). When
a block located in a multiblock carrier is shrunk,
the block will be moved if the ratio of the size of the returned
memory compared to the previous size is more than this threshold;
otherwise, the block will be shrunk at current location.
- rsbcmt ]]>
+ rsbcmt ]]>
-
Relative singleblock carrier move threshold (in percent). When
a block located in a singleblock carrier is shrunk to
@@ -506,7 +506,7 @@
the block will be left unchanged in the singleblock carrier if
the ratio of unused memory is less than this threshold;
otherwise, it will be moved into a multiblock carrier.
- rsbcst ]]>
+ rsbcst ]]>
-
Relative singleblock carrier shrink threshold (in
percent). When a block located in an mseg_alloc
@@ -514,20 +514,20 @@
unchanged if the ratio of unused memory is less than this
threshold; otherwise, the carrier will be shrunk.
See also asbcst.
- sbct ]]>
+ sbct ]]>
-
Singleblock carrier threshold. Blocks larger than this
threshold will be placed in singleblock carriers. Blocks
smaller than this threshold will be placed in multiblock
carriers. On 32-bit Unix style OS this threshold can not be set higher
than 8 megabytes.
- smbcs ]]>
+ smbcs ]]>
-
Smallest (mseg_alloc) multiblock carrier size (in
kilobytes). See the description
on how sizes for mseg_alloc multiblock carriers are decided
in "the alloc_util framework" section.
- t true|false]]>
+ t true|false]]>
-
Multiple, thread specific instances of the allocator.
This option will only have any effect on the runtime system
@@ -544,20 +544,20 @@
alloc_util, i.e. all allocators based on alloc_util
will be effected:
- ]]>
+ ]]>
-
sys_alloc carrier size. Carriers allocated via
sys_alloc will be allocated in sizes which are
multiples of the sys_alloc carrier size. This is not
true for main multiblock carriers and carriers allocated
during a memory shortage, though.
- ]]>
+ ]]>
-
Max mseg_alloc carriers. Maximum number of carriers
placed in separate memory segments. When this limit has been
reached, new carriers will be placed in memory retrieved from
sys_alloc.
- ]]>
+ ]]>
-
Allow sys_alloc carriers. By default true. If
set to false, sys_alloc carriers will never be
@@ -565,19 +565,19 @@
Instrumentation flags:
- +Mim true|false
+ +Mim true|false
-
A map over current allocations is kept by the emulator. The
allocation map can be retrieved via the instrument
module. +Mim true implies +Mis true.
+Mim true is the same as
-instr.
- +Mis true|false
+ +Mis true|false
-
Status over allocated memory is kept by the emulator. The
allocation status can be retrieved via the instrument
module.
- +Mit X
+ +Mit X
-
Reserved for future use. Do not use this flag.
@@ -587,7 +587,7 @@
Other flags:
- +Mea min|max|r9c|r10b|r11b|config
+ +Mea min|max|r9c|r10b|r11b|config
-
min
@@ -617,7 +617,7 @@
- +Mlpm all|no
+ +Mlpm all|no
- Lock physical memory. The default value is no, i.e.,
no physical memory will be locked. If set to all, all
memory mappings made by the runtime system, will be locked into
--
cgit v1.2.3