Skip to content
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

(0.48) Remove requirement for consistent memory page size in SCC #20183

Merged
merged 1 commit into from
Sep 18, 2024

Conversation

hangshao0
Copy link
Contributor

  1. The page level operation in SCC are msync and mprotect. msync is only used on z/OS for persistent cache, we can always do msync if we have a valid _osPageSize. For mprotect, it is turned off if the SCC is readonly. If the data is not paged aligned anymore, mprotect should be also be turned off. There is no need to force consistent memory page size between cold and warn runs anymore.

  2. Add new test flags and command line test cases.

  3. Add top layer page size infomation in cache stats.

  4. Add page size info into javacore.

Fixes #19968

Port of #19972

1. The page level operation in SCC are msync and mprotect. msync is only
used on z/OS for persistent cache, we can always do msync if we have a
valid _osPageSize. For mprotect, it is turned off if the SCC is
readonly. If the data is not paged aligned anymore, mprotect should be
also be turned off. There is no need to force consistent memory page
size between cold and warn runs anymore.

2. Add new test flags and command line test cases.

3. Add top layer page size infomation in cache stats.

4. Add page size info into javacore.

Fixes eclipse-openj9#19968

Signed-off-by: Hang Shao <hangshao@ca.ibm.com>
@hangshao0
Copy link
Contributor Author

@TobiAjila Could you merge this backport ?

@tajila tajila merged commit 7c2217e into eclipse-openj9:v0.48.0-release Sep 18, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants