RFR: 8256302: releasing oopStorage when deflating allows for faster deleting [v5]

Daniel D. Daugherty dcubed at openjdk.org
Sun Jun 4 14:23:17 UTC 2023


On Sun, 4 Jun 2023 14:18:41 GMT, Daniel D. Daugherty <dcubed at openjdk.org> wrote:

>> Releasing ObjectMonitor oopStorage earlier when deflating allows ObjectMonitor
>> deletion by a JavaThread (usually the MonitorDeflationThread) to happen while a
>> ThreadBlockInVM helper is in place. This should improve time-to-safepoint.
>
> Daniel D. Daugherty has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains five additional commits since the last revision:
> 
>  - Merge tag 'jdk-21+25' into JDK-8256302
>    
>    Added tag jdk-21+25 for changeset a46b5acc
>  - Allow ObjectMonitor::_object to be reset to nullptr when it is released which allows the code to be cleaner.
>  - Merge tag 'jdk-21+23' into JDK-8256302
>    
>    Added tag jdk-21+23 for changeset 6d4782bc
>  - address the easy dholmes and kimbarrett CR comments
>  - 8256302: releasing oopStorage when deflating allows for faster deleting

I rebased the project to jdk-21+25 and ran the usual Mach5 Tier[1-8]. The results
look great for Mach5 Tier[1-7] and Tier8 is chugging along:

https://bugs.openjdk.org/browse/JDK-8256302?focusedCommentId=14586793&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14586793

I believe the patch is again ready for reviews and I believe I've addressed all of
the previous comments. Please let me know if I missing something.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/11296#issuecomment-1575587500


More information about the hotspot-runtime-dev mailing list