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

SATB queue set should initialize and manage their own locks

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Withdrawn
    • Icon: P4 P4
    • tbd
    • 9, 10
    • hotspot
    • None
    • gc
    • generic
    • generic

      Currently there are 3 locks related to SATB queues, and they are declared and defined globally in mutexLocker.hpp|cpp. They are only initialized inside an if (UseG1GC) block. This is slightly problematic when another GC (e.g. Shenandoah) also needs to use SATB and their respective locks.
      In any case, it seems much cleaner to make those locks private in SATBQueueSet (or PtrQueueSet) and initialize them there and not expose it to the world to begin with.

            rkennke Roman Kennke
            rkennke Roman Kennke
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: