lib: nrf_provisioning: Add heap allocation option for HTTP buffers#38
Merged
Merged
Conversation
Signed-off-by: Dmitry Alexeev <dmitry.alexeev@emcraft.com>
wgroom-els
approved these changes
Jun 19, 2026
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.
Add CONFIG_NRF_PROVISIONING_USE_KMALLOC to allocate provisioning HTTP RX/TX buffers and codec data from the kernel heap instead of reserving them as permanent static memory.
This reduces static RAM usage by allocating the buffers only during a provisioning exchange and freeing them afterwards. The tradeoff is that the heap must be large enough to hold RX_BUF_SZ + TX_BUF_SZ and other
concurrent allocations.
Reuse the existing pointer-based codec layout used by USE_MALLOC; only the allocator differs (k_malloc/k_free vs malloc/free).