Draft
Conversation
Passes all tests, but does not free anything yet
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.
For small objects, this implementation of malloc maintains arenas of objects of the same size. Since all objects in these arenas are the same size, they can share a single header, allowing small allocations to be efficient. In the below table, efficiency is defined as (# bytes used for storing objects) / (# bytes allocated), using pages of 4096 bytes. If the efficiency is 50%, then for each 1 byte stored, there is 1 byte of overhead.
For allocations larger than the page size, it is assumed that the allocation will be aligned to the page.
Compared to a scheme with chunk headers of 8 bytes, this scheme is more efficient for allocations of size 1-128, but is a lot less efficient for larger allocations. However, it has the slight advantage that all large allocations are page-aligned.
It might be possible to combine this scheme with another scheme for allocations >= 256 (or 128) bytes. However, the current scheme reserves all allocations that are not aligned to the page size as a small allocation, so more might need to be added to differentiate between small allocations and large allocations, such as a hash table.