jdk17u-dev
jdk17u-dev copied to clipboard
openjdk
8276055: ZGC: Defragment address space
Reviewed-by: eosterlund, stefank
Progress
- [ ] Change must be properly reviewed (1 review required, with at least 1 Reviewer)
- [x] Change must not contain extraneous whitespace
- [ ] JDK-8276055 needs maintainer approval
- [x] Commit message must refer to an issue
Error
⚠️ OCA signatory status must be verified
Issue
- JDK-8276055: ZGC: Defragment address space (Enhancement - P4) ⚠️ Issue is already resolved. Consider making this a "backport pull request" by setting the PR title to
Backport <hash>with the hash of the original commit. See Backports.
Reviewing
Using git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/778/head:pull/778
$ git checkout pull/778
Update a local copy of the PR:
$ git checkout pull/778
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/778/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 778
View PR using the GUI difftool:
$ git pr show -t 778
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/778.diff
backport from openjdk18, this patch is useful to fix some out of address space problem, in my case it can reduce the probability of my problem when use zgc
Hi @AnjianWen, welcome to this OpenJDK project and thanks for contributing!
We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.
If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user AnjianWen" as summary for the issue.
If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.
![bridgekeeper[bot] avatar](https://avatars.githubusercontent.com/u/41768318?v=4 "Published by a pub.dev verified publisher"){kind=small}
Thank you! Please allow for up to two weeks to process your OCA, although it is usually done within one to two business days. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!
@AnjianWen This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!
since last commit，I have been testing for nearly a month，the fragment problem happens in a very low probability，so the patch alleviate this problem to some extent. it might be backport to jdk17？need someone review
@AnjianWen This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!
@AnjianWen This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.
❗ This change is not yet ready to be integrated. See the Progress checklist in the description for automated requirements.
@AnjianWen This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!
@AnjianWen This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.