feat: add linear allocator implementation#3132
Open
B33Boy wants to merge 7 commits intoTheAlgorithms:masterfrom
Open
feat: add linear allocator implementation#3132B33Boy wants to merge 7 commits intoTheAlgorithms:masterfrom
B33Boy wants to merge 7 commits intoTheAlgorithms:masterfrom
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
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.
Description of Change
I've implemented a simple linear (bump) allocator under a new
memory/subdirectory, intended to house memory management algorithms (e.g. pool, stack, free list allocators).Description of Implementation
A linear allocator pre-allocates a fixed block of memory and hands it out to the user sequentially. It consists of a buffer and an offset. This offset gets bumped forward after each allocation, and adheres to memory alignment requirements.
My implementation manages a buffer that is stack-allocated via a templated parameter. It is faster than malloc because allocation is O(1), there are no locks used, and there is no external memory fragmentation (memory is contiguous and the only waste is padding due to alignment). The tradeoff is losing the ability to have individual de-allocations. Futhermore, the lifetime is tied to the scope of usage, so it is best suited for scenarios where you are working with objects that share the same lifetime.
Why is this educational?
My implementation exposes the mechanics of allocators such as:
alignof,alignasChecklist
Notes: Add a linear allocator implementation under new
memory/subdirectory