std.heap.PageAllocator updates to fix race condition and utilize NtAllocateVirtualMemory / NtFreeVirtualMemory instead of VirtualAlloc / VirtualFree #23097
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 PR attempts to address some of the concerns outlined in #22846
Two new functions (
NtAllocateVirtualMemory
andNtFreeVirtualMemory
) were added tontdll.zig
andwindows.zig
as an FFI signature and Zig wrapper, respectively.Changes made to
std.heap.PageAllocator
include:Usage of
VirtualAlloc
andVirtualFree
has been replaced with their respective NT counterpart and memory allocations are now using placeholder constants to prevent the race condition previously present. Lastly, instead of freeing the entire region - the unaligned portions at the head and tail of the region are freed which should improve performance.