Re: [PATCH v2 1/3] mutex: Make more scalable by doing less atomic operations

On 04/15/2013 10:37 AM, Waiman Long wrote: In the __mutex_lock_common() function, an initial entry into the lock slow path will cause two atomic_xchg instructions to be issued. Together with the atomic decrement in the fast path, a total of three atomic read-modify-write instructions will be

[PATCH v2 1/3] mutex: Make more scalable by doing less atomic operations

In the __mutex_lock_common() function, an initial entry into the lock slow path will cause two atomic_xchg instructions to be issued. Together with the atomic decrement in the fast path, a total of three atomic read-modify-write instructions will be issued in rapid succession. This can cause a lot

[PATCH v2 1/3] mutex: Make more scalable by doing less atomic operations

In the __mutex_lock_common() function, an initial entry into the lock slow path will cause two atomic_xchg instructions to be issued. Together with the atomic decrement in the fast path, a total of three atomic read-modify-write instructions will be issued in rapid succession. This can cause a lot

Re: [PATCH v2 1/3] mutex: Make more scalable by doing less atomic operations

On 04/15/2013 10:37 AM, Waiman Long wrote: In the __mutex_lock_common() function, an initial entry into the lock slow path will cause two atomic_xchg instructions to be issued. Together with the atomic decrement in the fast path, a total of three atomic read-modify-write instructions will be