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

Consider removing stale cards from HCC during cleanup

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Closed
    • Priority: P4
    • Resolution: Won't Fix
    • Affects Version/s: 9
    • Fix Version/s: 10
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
      gc
    • CPU:
      generic
    • OS:
      generic

      Description

      Some of the complexity in refine_card / oops_on_card_seq_iterate_careful arises from the possibility of "stale" marked cards, especially during concurrent refinement. These are cards in regions that have been freed and then possibly reallocated. At present the only source of stale cards in the concurrent case seems to be HCC eviction. (Eager reclaim of humongous objects flushes relevant remembered sets (possibly containing stale entries) for reconsideration during that GC, but in-GC card clipping to scan_top deals with that.) Doing HCC cleanup when freeing regions might remove the need for klass_or_null checking in the humongous case for concurrent refinement.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              kbarrett Kim Barrett
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: