diff options
| author | fanquake <fanquake@gmail.com> | 2023-09-24 18:54:10 +0100 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2023-09-24 18:54:16 +0100 |
| commit | dcfbf3c2107c3cb9d343ebfa0eee78278dea8d66 (patch) | |
| tree | 08100601d1952517d4e759096fdb16cf61d11fca /test | |
| parent | ac9fa6ec78158e41006d621ee62e44dec0f934c0 (diff) | |
| parent | 12f7257b8f6ba0de1fb05b598e916c8b14bcab8c (diff) | |
| download | bitcoin-dcfbf3c2107c3cb9d343ebfa0eee78278dea8d66.tar.xz | |
Merge bitcoin/bitcoin#28512: doc: Be vague instead of wrong about MALLOC_ARENA_MAX
12f7257b8f6ba0de1fb05b598e916c8b14bcab8c doc: Be vague instead of wrong about MALLOC_ARENA_MAX (Tim Ruffing)
Pull request description:
Before this commit, we claim that glibc's malloc implementation uses 2 arenas by default. But that's true only on 32-bit systems, and even there, it uses *up* to 2 arenas.
This commit fixes the wrong statement. The new statement is intentionally vague to reduce our maintenance burden.
For details, see:
https://www.gnu.org/software/libc/manual/html_node/Memory-Allocation-Tunables.html#index-glibc_002emalloc_002earena_005fmax
Noticed in:
https://github.com/bitcoin/bitcoin/pull/27642#issuecomment-1728103427
ACKs for top commit:
fanquake:
ACK 12f7257b8f6ba0de1fb05b598e916c8b14bcab8c
Tree-SHA512: c0ff1e35b682a841e366a1cad26e18ff79a93d97103529be35a972c7dcbb95f5354e7a7b98a86731f491434d64685bb58cc3cc9100f0577d8f75db05e951b09a
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions