comparison: docs/Writerside/topics/memory.md
docs/Writerside/topics/memory.md
- branch
- docs/3.1
- changeset 1170
- 49cc0bbea6a9
- parent 1141
- a06a2d27c043
- child 1210
- 2ad0cf0f314b
equal
deleted
inserted
replaced
| 1169:6a33a5648027 | 1170:49cc0bbea6a9 |
|---|---|
| 1 # Memory Management | 1 # Memory Management |
| 2 | |
| 3 With the `CxAllocator` interface UCX provides the possibility to use custom allocator functions for different purposes. | |
| 4 Many UCX functions support the use of specialized allocators or provide a second function suffixed with `_a`. | |
| 5 | |
| 6 For convenience, functions that are not explicitly requesting an allocator - like e.g. `cx_strdup_a()` - also accept | |
| 7 `NULL` as an allocator, in which case the `cxDefaultAllocator` and stdlib functions are used. | |
| 8 | |
| 9 Additionally, UCX also provides a [memory pool](mempool.h.md) implementation of the allocator interface. | |
| 10 | |
| 11 > Although not part of the public API, UCX is also implementing the allocator interface | |
| 12 > in its own test suite: `CxTestingAllocator`. This allocator keeps track of memory allocations | |
| 13 > and de-allocations with the goal to detect memory management errors. |
