Simplify concurrent refinement thread deactivation

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P4
    • 9
    • Affects Version/s: 9
    • Component/s: hotspot
    • gc
    • b109
    • generic
    • generic

      Concurrent refinement threads explicitly compare the current number of buffers with their deactivation threadhold to determine whether to deactivate. They also call apply_closure_to_completed_buffer with a "stop_at" of the green zone value, and deactivate if it returns false. It would be simpler to skip the explicit check for deactivation and just call apply_closure_to_completed_buffer with the deactivation threshold as the stop_at value.

            Assignee:
            Kim Barrett
            Reporter:
            Kim Barrett
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: