[FFI/0.36]Fix the OOM issue with thunk allocation #16445
Merged
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
The changes aim to address the OOM issue with thunk allocation on the platforms with a small page size (e.g. 4KB) by maintaining a thunk heap list in which case a new thunk heap is created only when there is no free thunk heap available in the list to allocate thunk. Signed-off-by: Cheng Jin <jincheng@ca.ibm.com>
pshipton
approved these changes
Dec 8, 2022
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.
The changes aim to address the OOM issue with thunk allocation on
the platforms with a small page size (e.g. 4KB) by maintaining a thunk
heap list in which case a new thunk heap is created only when there
is no free thunk heap available in the list to allocate thunk.
Cherry pick of #16260 for 0.36