Move G1 concurrent refinement adjustment code out of G1CollectorPolicy

XMLWordPrintable

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

      As the title says,
      G1CollectorPolicy::adjust_concurrent_refinement should be moved out of the policy, it relies on none of the values from the policy, except for a few timings.
      It almost exclusively calls methods on ConcurrentG1Refine so it most likely fits in nicely in that class.

            Assignee:
            Mikael Gerdin (Inactive)
            Reporter:
            Mikael Gerdin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: