Expose base_alloc as a pool in public API #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
which supports arbitrary size allocations and routes the alloc requests to specific allocation classes or to ba_alloc_os. Use this abstraction instead of a single global pool of fixed size.
igchor
force-pushed
the
ba_alloc_classes
branch
6 times, most recently
from
39bdc38 to
197ab24
Compare
igchor
pushed a commit
that referenced
this pull request
Mar 5, 2024
Revised API documentation theme
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Expose base_alloc as a pool in public API. It can be used by users to allocate metadata for their providers/pools.
The core libumf (libumf.so/.a) accesses the pool API through umf_ba_global_alloc/free functions for allocating umf_memory_pool_t, umf_memory_provider_t etc. to avoid infinite recursion. There is no recursion problem in external libs.