8321137: Reconsider ICStub alignment#17277
Conversation
|
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
Webrevs
|
dean-long
left a comment
There was a problem hiding this comment.
Nice job minimizing the changes.
|
@shipilev 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 28 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 |
|
Thanks @dean-long! Any other takers? Notably, I would like opinions of platform maintainers: @theRealAph, @TheRealMDoerr, @RealFYang, @bulasevich. |
|
It's probably good, but are you aware of the plans to remove the ICStubs completely? @fisk may have an opinion on it. |
Yes, I did x86_32 version for Erik. I think we want something we can support in JDK update releases. I think the ICStub removal would not be backportable at all. |
|
Ok. I think it's good for backports. I'll put it in our test queue. |
fisk
left a comment
There was a problem hiding this comment.
Seems like a reasonable band-aid to backport. Looks good.
TheRealMDoerr
left a comment
There was a problem hiding this comment.
Test results are good. Thumbs up from my side!
RealFYang
left a comment
There was a problem hiding this comment.
LGTM. Also performed tier1-3 test with fastdebug build on linux-riscv64 platform.
|
OK, thanks! I am going to merge it, and look for follow-ups, if any. /integrate |
|
Going to push as commit 7be9f1d.
Your commit was automatically rebased without conflicts. |
This continues from #16911. It initially started as performance optimization to compact
ICStubs, but I think the safety arguments for fitting theICStubper instruction cache line prevails. See bug and previous PR for more gory details. The footprint improvements on some architectures come as side-effect of untying theICStubsize fromCodeEntryAlignmentto (sometimes lower) cache line size.Note that the size of
ICStubis important, becauseICBufferis small (10K by default), and its depletion causes theICBufferFullsafepoint. I would make a (separate) argument to bump the defaultICBuffersize a bit to make it less important.Current patch affects
ICStubsize in different ways on different platforms, since current size is effectively 2xCodeEntryAlignmentand new size is cache line size:Additional testing:
tier{1,2,3,4}tier{1,2,3,4}Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17277/head:pull/17277$ git checkout pull/17277Update a local copy of the PR:
$ git checkout pull/17277$ git pull https://git.openjdk.org/jdk.git pull/17277/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17277View PR using the GUI difftool:
$ git pr show -t 17277Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17277.diff
Webrev
Link to Webrev Comment