[PATCH] nptl: Add backoff mechanism to spinlock loop
Noah Goldstein
goldstein.w.n@gmail.com
Fri Mar 25 01:58:35 GMT 2022
On Thu, Mar 24, 2022 at 8:51 PM Wangyang Guo via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> When mutiple threads waiting for lock at the same time, once lock owner
> releases the lock, waiters will see lock available and all try to lock,
> which may cause an expensive CAS storm.
>
> Binary exponential backoff with random jitter is introduced. As try-lock
> attempt increases, there is more likely that a larger number threads
> compete for adaptive mutex lock, so increase wait time in exponential.
> A random jitter is also added to avoid synchronous try-lock from other
> threads.
>
> Signed-off-by: Wangyang Guo <wangyang.guo@intel.com>
> ---
> nptl/pthread_mutex_lock.c | 17 +++++++++++++++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/nptl/pthread_mutex_lock.c b/nptl/pthread_mutex_lock.c
> index d2e652d151..ec57dc3627 100644
> --- a/nptl/pthread_mutex_lock.c
> +++ b/nptl/pthread_mutex_lock.c
> @@ -26,6 +26,7 @@
> #include <futex-internal.h>
> #include <stap-probe.h>
> #include <shlib-compat.h>
> +#include <random-bits.h>
>
> /* Some of the following definitions differ when pthread_mutex_cond_lock.c
> includes this file. */
> @@ -138,14 +139,26 @@ PTHREAD_MUTEX_LOCK (pthread_mutex_t *mutex)
> int cnt = 0;
> int max_cnt = MIN (max_adaptive_count (),
> mutex->__data.__spins * 2 + 10);
> + int spin_count, exp_backoff = 1;
> + unsigned int jitter = random_bits ();
> do
> {
> - if (cnt++ >= max_cnt)
> + /* In each loop, spin count is exponential backoff plus
> + random jitter, random range is [0, exp_backoff-1]. */
> + spin_count = exp_backoff + (jitter & (exp_backoff - 1));
> + cnt += spin_count;
> + if (cnt >= max_cnt)
> {
> + /* If cnt exceeds max spin count, just go to wait
> + queue. */
> LLL_MUTEX_LOCK (mutex);
> break;
> }
> - atomic_spin_nop ();
> + do
> + atomic_spin_nop ();
> + while (--spin_count > 0);
> + /* Binary exponential backoff, prepare for next loop. */
> + exp_backoff <<= 1;
> }
> while (LLL_MUTEX_READ_LOCK (mutex) != 0
Does this load not already prevent against the 'CAS storm'?
> || LLL_MUTEX_TRYLOCK (mutex) != 0);
> --
> 2.35.1
>
More information about the Libc-alpha
mailing list