Inferencium/website
1
0
Fork 0
Code Issues Activity

Mention potential memory fragmentation due to too-high arena count

Browse Source
This commit is contained in:
inference 2024-01-29 18:55:00 +00:00
parent 32e873ae32
commit e3ba86d7ca
Signed by: inference
SSH Key Fingerprint: SHA256:FtEVfx1CmTKMy40VwZvF4k+3TC+QhCWy+EmPRg50Nnc
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
documentation/hardened_malloc.xhtml
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<!-- Inferencium - Website - Documentation - hardened_malloc -->
<!-- Version: 3.0.0-alpha.5 -->
<!-- Version: 3.0.0-alpha.6 -->
<!-- Copyright 2023 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause -->
@ -73,10 +73,11 @@
<p><code>CONFIG_N_ARENA=<var>n</var></code> can be adjusted to increase parallel
performance at the expense of memory usage, or decrease memory usage at the expense of
parallel performance, where <var>n</var> is an integer. Higher values prefer parallel
performance, lower values prefer lower memory usage. The number of arenas has no impact
on the security properties of hardened_malloc.<br/>
<b>Minimum number of arenas:</b> 1<br/>
<b>Maximum number of arenas:</b> 256</p>
performance, whereas lower values prefer lower memory usage. Note that having too many
arenas may cause memory fragmentation and decrease system performance. The number of
arenas has no impact on the security properties of hardened_malloc.</p>
<p><b>Minimum number of arenas:</b> 1</p>
<p><b>Maximum number of arenas:</b> 256</p>
<p>For extra security, <code>CONFIG_SEAL_METADATA=true</code> can be used in order to
control whether Memory Protection Keys are used to disable access to all writable
allocator state outside of the memory allocator code. It's currently disabled by default