Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8246101

Shenandoah: consider walking CLDG without _claim_strong

    Details

    • Type: Enhancement
    • Status: New
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: 8-shenandoah, 11-shenandoah, 14, 15
    • Fix Version/s: None
    • Component/s: hotspot
    • Subcomponent:
      gc

      Description

      As the more complicated followup for JDK-8246097, we might even consider walking the CLDG without _claim_strong and avoid clearing the marks before the walk. The only problem is that we need to make sure every path does _claim_none. And there are, unfortunately, paths through shared OopIterateClosures that default to _claim_strong, for example MetadataVisitingOopIterateClosure.

      POC:
       http://cr.openjdk.java.net/~shade/8246101/8246101-poc.patch

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                shade Aleksey Shipilev
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: