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
Update to avoid initial LOA size is smaller than largeObjectMinimumSize #4860
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
LinHu2016
requested review from
charliegracie,
rwy7 and
youngar
as code owners
February 24, 2020 20:53
local test result: ./java -Xms1m -verbose:gc -version
|
@amicic @dmitripivkine please review the change, thanks |
LinHu2016
force-pushed
the
PR143196
branch
4 times, most recently
from
February 26, 2020 18:33
dcc70d4
to
4b5d839
Compare
amicic
reviewed
Mar 2, 2020
amicic
reviewed
Mar 2, 2020
amicic
reviewed
Mar 2, 2020
amicic
reviewed
Mar 2, 2020
LinHu2016
force-pushed
the
PR143196
branch
3 times, most recently
from
March 4, 2020 21:23
4238fed
to
e5ed6a7
Compare
amicic
approved these changes
Mar 10, 2020
@youngar or @rwy0717, please proceed with further review |
@genie-omr build all |
@genie-omr build aix |
youngar
suggested changes
Mar 19, 2020
lgtm with a couple nitpicks |
LOA size should be bigger than largeObjectMinimumSize, otherwise the assertion would be triggered during allocation. small initial heap size via custom Xms option might cause the case. Update the code to set LOA = 0 if initial LOA size is smaller than largeObjectMinimumSize. - use inline function checkAndSetSizeForLOA() to reduce code duplication. Signed-off-by: Lin Hu <linhu@ca.ibm.com>
youngar
approved these changes
Mar 26, 2020
@genie-omr build all |
ignoring z/os due to infrastructure issue |
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.
Signed-off-by: Lin Hu linhu@ca.ibm.com