(0.56) RAM Class: Per-kind segment allocation and sizing #22578
Merged
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.
Introduce distinct segment categories (
SUB4G
,FREQUENTLY_ACCESSED
,INFREQUENTLY_ACCESSED
).Separates hot vs. cold
J9Class
data for better memory efficiency.SUB4G
segments are sized in multiples of alignedJ9Class
headersand tagged with
MEMORY_TYPE_RAM_CLASS_SUB4G
.Related: #20644
Depends on eclipse-omr/omr#7916
Depends on eclipse-openj9/openj9-omr#249
Backport of #22530