-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8354358: ZGC: ZPartition::prime handle discontiguous reservations correctly #24589
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
👋 Welcome back aboldtch! A progress list of the required criteria for merging this PR into |
@xmas92 This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. 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 27 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. ➡️ To integrate this PR with the above commit message to the |
Webrevs
|
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 good.
As a follow-up, we might want to move the pre-touching so that we don't start and stop threads multiple times.
const ZVirtualMemory vmem = claim_virtual(size); | ||
const size_t claimed_size = claim_virtual(size, &vmems); | ||
|
||
// Each partition must have at least size total vmems available when priming. |
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.
Maybe something like "The partition must have size available in virtual memory when priming"? I'm reading this as the number of vmems, not the size of them combined.
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 good. As you say, this is nicely implemented with features from the Mapped Cache.
Thanks for the reviews. |
Going to push as commit 97e1075.
Your commit was automatically rebased without conflicts. |
Prior to JDK-8350441 the VM would not have started if we received a discontiguous heap reservation with all reservations smaller than the inital heap capacity. Now we crash because
ZPartition::prime
does not take this into account.However in contrast to the page cache, the mapped cache makes it trivial to support this scenario. So I propose fixing
ZPartition::prime
to handle any discontiguous heap reservation.Can be provoked in a debug build by using ZForceDiscontiguousHeapReservations > 16
java -XX:+UseZGC -XX:ZForceDiscontiguousHeapReservations=17 -Xmx128m -Xms128m --version
Currently running this through testing.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24589/head:pull/24589
$ git checkout pull/24589
Update a local copy of the PR:
$ git checkout pull/24589
$ git pull https://git.openjdk.org/jdk.git pull/24589/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24589
View PR using the GUI difftool:
$ git pr show -t 24589
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24589.diff
Using Webrev
Link to Webrev Comment