allocator_api: provide a grow_zeroed implementation #99
Conversation
This file contains 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
|
(there is some noise due to rustfmt, which I forgot to run in the initial implementation, let me know if you want me to drop it). |
Fixup fitzgen#98 Signed-off-by: Arthur Gautier <[email protected]>
baloo
force-pushed
the
baloo/allocator/grow_zeroed
branch
2 times, most recently
from
0ef0606
to
610fe53
Compare
Signed-off-by: Arthur Gautier <[email protected]>
baloo
force-pushed
the
baloo/allocator/grow_zeroed
branch
from
610fe53
to
b1c1b2a
Compare
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.
Fixup #98
The current implementation of grow_zeroed in liballoc allocates a new chunk, copies data over, then deallocates the old chunk.
Bumpalo can use a more memory efficient version of that, and this is an implementation of it.