Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-14529

InnoDB rw-locks: optimize memory barriers

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.3.2
    • Fix Version/s: 10.3.3
    • Component/s: Server
    • Labels:
      None
    • Environment:
      Ubuntu 16.02 on Arm 64 bit platform

      Description

      Hi,

      I see __atomic_compare_exchange_n function is being called with different memory order while
      doing the same type of atomic operation. In spin lock ACQUIRE AND RELAX being used

      but in rw_lock_lock_word_decr function

      i see __ATOMIC_SEQ_CST being hard coded in the cmpxchng. I feel we can use consistenly use ACQUIRE AND RELAX memory order for all the mutex implemenation in all the platform.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                svoj Sergey Vojtovich
                Reporter:
                ssethia Sandeep sethia
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: