Add per-instance custom memory allocator interface - #235
Merged
Conversation
Encoder/decoder route all internal allocations through a caller-supplied oapv_ops_mem_t (via cdesc.ops_mem), defaulting to the standard C library. Signed-off-by: KP Choi <kp5.choi@samsung.com>
Signed-off-by: KP Choi <kp5.choi@samsung.com>
Signed-off-by: KP Choi <kp5.choi@samsung.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This adds a way for applications to supply their own memory allocator, as discussed in #228.
oapv_ops_mem_tinterface (malloc/calloc/realloc/freeplus an opaqueudata), passed through the creation descriptors:oapve_cdesc_t,oapvd_cdesc_t, and a newoapvm_cdesc_tfor the metadata containermalloc/freecalls remain in the libraryops_memasNULLkeeps the standard C library behavior; there is no global allocator stateoapvm_create()now takes a descriptor argument, so metadata container callers need a small updateUsage is documented in the "Custom memory allocator" section of the README.