core/memory: Pooled memory implementation #1085
Draft
+321
−9
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
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.
Pooled memory is, under the hood, direct memory partitioned in 64 KiB blocks, with the difference that developers don't have to be aware of physical addresses and only care about the virtual address space, which can make allocations easier for the developer.
The memory pool can be expanded (direct memory is allocated for pool usage and can no longer be used as normal direct memory), reserved (reserved area must be aligned to 2MB or a multiple of it), committed, and decommitted.
This PR lacks memory pool batching and getting block statistics, but I haven't seen any game using these.
Frequently used by newer revisions of Unreal Engine.