Dedicated nursery memory area#1861
Draft
timo wants to merge 4 commits into
Draft
Conversation
05ef27b to
c970e28
Compare
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.
This feature reserves a big virtual memory area during startup (0x40000000 bytes, so 1 gigabyte. this should maybe be more, since virtual memory is essentially free) and gives it to mimalloc for use to allocate nurseries in.
This lets us check very cheaply if a pointer points into a nursery, or somewhere else. Most importantly, checking if an object is in generation two now becomes a simple bounds check on the pointer (plus check if the feature is currently in use, since the virtual memory reservation at the start can fail) instead of having to follow the pointer which is not guaranteed to hit the processor cache (especially in a minor gc collection run).