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

Remove Type-Stable-Memory support for Parkers

    XMLWordPrintable

Details

    • b07

    Description

      TSM for Parkers was introduced by JDK-6271298 (there's a typo in the comment in park.hpp that transposes the last 2 numbers of the bug). But since JDK-8167108 introduced Thread Safe-Memory-Reclaimation (SMR) there has been no need to issue the unpark outside the scope of the ThreadsListHandle and so no need to rely on TSM. Once we move the unpark we can remove TSM support and simplify the code.

      Need to confirm that no other Parker usage has also come to rely on TSM.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDK-8167108 inconsistent handling of SR_lock can lead to crashes

          • P3 - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-6271298 java.util.concurrent unpark() may reference stale native thread structures

          • P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Enhancement - null JDK-8222518 Remove unnecessary caching of Parker object in java.lang.Thread

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          links to

          Commit Commit openjdk/jdk/77a43023

          Review Review openjdk/jdk/2089

          Activity

            People

              dholmes David Holmes
              dholmes David Holmes
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: