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

Recursive lightweight locking

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Delivered
    • Icon: P4 P4
    • 23
    • None
    • hotspot

      Add support for a limited set of recursive (reentrant) locking for LM_LIGHTWEIGHT.

      The current implementation of LM_LIGHTWEIGHT must inflate the monitor for any recursive locking.

      This enhancement proposes introducing the ability for LM_LIGHTWEIGHT to handle consecutive recursive monitor enter. Limiting the implementation to only consecutive monitor enters allows for more efficient emitted code which only needs to look at the two top most entries on the lock stack to determine what to do in a monitor exit.

      A high level overview:
        * Locking is still performed on the mark word
          * Unlocked (0b01) <=> Locked (0b00)
        * Monitor enter on Obj with mark word Unlocked (0b01) is the same
          * Transition Obj's mark word Unlocked (0b01) => Locked (0b00)
          * Push Obj onto the lock stack
          * Success
        * Monitor enter on Obj with mark word Locked (0b01) will check the top entry on the lock stack
          * If top entry is Obj
            * Push Obj on the lock stack
            * Success
          * If top entry is not Obj
            * Inflate and call ObjectMonitor::enter
        * Monitor exit on Obj with mark word Locked (0b01) will check the two top entries on the lock stack
          * If just the top entry is Obj
            * Transition Obj's mark word Locked (0b00) => Unlocked (0b01)
            * Pop the entry
            * Success
          * If both entries are Obj
            * Pop the top entry
            * Success
          * Any other case only occurs for unstructured locking, then just inflate and call ObjectMonitor::exit
        * If the monitor has been inflated for object Obj which is owned by the current thread
          * All corresponding entries for Obj is removed from the lock stack
          * The monitor recursions is set to the number of removed entries - 1
          * The owner is changed from anonymous to the thread
          * The regular ObjectMonitor::action is called.

      The fundamental difference is that inflation must set the correct number of recursions when fixing the anonymous owner, and the lock stack must be checked for recursions when performing monitor exit to see if it is valid to transition the mark word to unlocked.

            aboldtch Axel Boldt-Christmas
            aboldtch Axel Boldt-Christmas
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: