From c7dc896e8897988ccc033e18fa19670ba7160565 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?John=20H=C3=B6gberg?=
Date: Thu, 3 May 2018 12:37:49 +0200
Subject: Allow cross-type carrier migration
---
erts/doc/src/erts_alloc.xml | 11 +++++------
1 file changed, 5 insertions(+), 6 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 a094217959..962bc9a244 100644
--- a/erts/doc/src/erts_alloc.xml
+++ b/erts/doc/src/erts_alloc.xml
@@ -487,11 +487,10 @@
utilization value used. Once a carrier is abandoned, no new
allocations are made in it. When an allocator instance gets an
increased multiblock carrier need, it first tries to fetch an
- abandoned carrier from an allocator instance of the same
- allocator type. If no abandoned carrier can be fetched, it
- creates a new empty carrier. When an abandoned carrier has been
- fetched, it will function as an ordinary carrier. This feature has
- special requirements on the
+ abandoned carrier from another allocator instance. If no abandoned
+ carrier can be fetched, it creates a new empty carrier. When an
+ abandoned carrier has been fetched, it will function as an ordinary
+ carrier. This feature has special requirements on the
allocation strategy used. Only
the strategies aoff, aoffcbf, aoffcaobf,
ageffcaoffm, ageffcbf and ageffcaobf
@@ -584,7 +583,7 @@
carriers are decided in section
The alloc_util Framework. On
- 32-bit Unix style OS this limit cannot be set > 128 MB.
+ 32-bit Unix style OS this limit cannot be set > 64 MB.
mbcgs ]]>
-
--
cgit v1.2.3