Clarify alignment requirements for MapViewOfFile3 #799
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
It has been observed that when using the MEM_REPLACE_PLACEHOLDER flag the input alignment isn't forced to 64k, you can use VirtualFreeEx with the MEM_PRESERVE_PLACEHOLDER to create an unaligned placeholder then pass that to MapViewOfFile3 to map a non-64k aligned region.
|
@bylaws : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Karl-Bridge-Microsoft
approved these changes
Jul 9, 2021
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.
It has been observed that when using the MEM_REPLACE_PLACEHOLDER flag the input alignment isn't forced to 64k, you can use VirtualFreeEx with the MEM_PRESERVE_PLACEHOLDER to create an unaligned placeholder then pass that to MapViewOfFile3 to map a non-64k aligned region.