Skip to content

(0.44) Correct memorypool usage calculating for GMP case #19168

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 18, 2024

Conversation

LinHu2016
Copy link
Contributor

@LinHu2016 LinHu2016 commented Mar 18, 2024

There was a gcEnd condition check patch for calculating memorypool usage at the end of GC due to the increment logic age for regions happened after getHeapMemorySnapshot(), but incrementing region's age has been updated to be called before getHeapMemorySnapshot(), condition check for gcEnd is unnecessory, also the condition check would cause incorrect memory usages for eden, reserved and survivor pools in Global Marking Phase case.

-cleanup the format base on the coding standard
UDATA to uintptr_t
"*" to " *"

Port of #19063 to 0.44

There was a gcEnd condition check patch for calculating memorypool usage
at the end of GC due to the increment logic age for regions happened
after getHeapMemorySnapshot(), but incrementing region's age has been
updated to be called before getHeapMemorySnapshot(), condition check for
gcEnd is unnecessory, also the condition check would cause incorrect
memory usages for eden, reserved and survivor pools in Global Marking
Phase case.

-cleanup the format base on the coding standard
 UDATA to uintptr_t
 "<type>*" to "<type> *"

Signed-off-by: hulin <[email protected]>
@pshipton pshipton changed the title Correct memorypool usage calculating for GMP case (0.44) Correct memorypool usage calculating for GMP case Mar 18, 2024
@pshipton pshipton merged commit 69b8c29 into eclipse-openj9:v0.44.0-release Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants