Alternative approach to page allocation #301
Closed
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
This is a direct style, not using arenas. It's more like a slab allocator, but only for 4k page allocations. This allows the slab cache to be manipulated only using atomic IORef operations.
dcoutts
force-pushed
the
dcoutts/page-alloc
branch
from
9bd992e to
3070863
Compare
|
Closed in favour of a new issue #760. We might revive the |
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.
This is here for benchmarking comparison purposes, and so see what we think of the generality vs performance trade-off.
This allocator approach is a direct style, not using arenas. It's more like a slab allocator, but only for 4k page allocations.
This allows the slab cache to be manipulated only using atomic IORef operations.