-
Notifications
You must be signed in to change notification settings - Fork 778
Changes to memory disclaim heuristics #23049
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
Conversation
|
jenkins test sanity.function all jdk21 |
9b9ce2a to
61a66c4
Compare
|
I discovered a potential 32-bit overflow when shifting |
|
jenkins test sanity.function all jdk21 |
|
jenkins test sanity.functional all jdk21 |
|
There were two failures: On Windows two SCC tests failed, mostly when trying to destroy a SCC: |
|
The same failures occurred again in small grinders. The platforms involved, AIX and Windows, do not use disclaiming. I am going to slightly change the code to be absolutely sure that we don't execute any of the disclaiming code on platforms other than Linux. |
This commit performs the following changes to memory disclaim heuristics: - The prefered location for disclaimed memory is now swap (used to be /tmp) - If swap is not available (or disallowed through -Xjit:dontDisclaimMemoryOnSwap) then the JIT will attempt to use /tmp - Disclaim is avoided if less than 1GB of disk space is available (on swap or /tmp respectively). This threshold can be changed with -Xjit:minDiskSpaceForDisclaim=<NNN> (in MB) Signed-off-by: Marius Pirvu <mpirvu@ca.ibm.com>
61a66c4 to
4033022
Compare
|
jenkins test sanity all jdk21 |
|
FYI @JamesKingdon since some of our customers raised issues with respect to disclaiming. |
|
jdk11 win failure is infra related: |
|
All the tests passed except the one on windows due to infra. |
This commit performs the following changes to memory disclaim heuristics: