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

Introduce ordering semantics for Atomic::add and other RMW atomics

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P2
    • Resolution: Fixed
    • Affects Version/s: 11
    • Fix Version/s: 11
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      b13

      Description

      Atomic::add is currently specified as "<fence> add-value-to-dest <membar StoreLoad|StoreStore>". However, this specification is not followed by all platforms. Especially on PPC64, this very conservative memory ordering is not desirable for performance critical usages.
      At the moment, there is one place where it's known that the memory barriers on PPC64 and s390 are not sufficient which was recently introduced by JDK-8195099 (Concurrent safe-memory-reclamation mechanism).
      Therefore, we should have configurable semantics similar to the ones introduced for Atomic::cmpxchg with JDK-8155949.

      The same applies to the remaining read-modifiy-write atomics.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mdoerr Martin Doerr
              Reporter:
              mdoerr Martin Doerr
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: