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
8265239: Shenandoah: Shenandoah heap region count could be off by 1 #3504
Conversation
|
@zhengyu123 The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine.
@zhengyu123 This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 37 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.
|
/integrate |
@zhengyu123 Since your change was applied there have been 42 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit ff5bb8c. |
henandoah uses MaxHeapSize to calculate region size, then aligns up heap size to region size alignment, but when it calculates region count, it does not take alignment into account, that may result 1 region short than actual count.
MaxHeapSize eventually aligns to HeapAlignment (which is region size in Shenandoah case) in GCArguments::initialize_heap_flags_and_sizes(), but it is too late.
Test:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3504/head:pull/3504
$ git checkout pull/3504
Update a local copy of the PR:
$ git checkout pull/3504
$ git pull https://git.openjdk.java.net/jdk pull/3504/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3504
View PR using the GUI difftool:
$ git pr show -t 3504
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3504.diff