From f231175d97338fef850723ab324b76c914008f42 Mon Sep 17 00:00:00 2001 From: Aravinth Manivannan Date: Sat, 13 Apr 2024 16:31:56 +0530 Subject: [PATCH] fix: update tests to reflect new permanent linking scheme --- tests/7158b1cdd50c.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/7158b1cdd50c.html b/tests/7158b1cdd50c.html index 1e0f305..17eb63d 100644 --- a/tests/7158b1cdd50c.html +++ b/tests/7158b1cdd50c.html @@ -149,7 +149,7 @@ rel="noreferrer"> Open post in medium.com
}
+ }
}
See gist on GitHub

Even though a spinlock is burning power in a tight loop until it succeeds, it actually is sometimes preferred over a traditional mutex. Traditional mutexes put a thread to sleep when they block, increasing the minimum latency for acquiring them from another thread. Modern mutexes are often a hybrid approach between a spinlock and a traditional mutex. Hybrid mutexes will attempt to acquire the lock quickly in userspace using atomic operations, without giving away their kernel-scheduled appointment on the CPU core. If the gambit didn’t pan out, the hybrid mutex will put the thread to sleep with a blocking syscall.

@@ -177,7 +177,7 @@ rel="noreferrer"> Open post in medium.com
}
+ }
}
See gist on GitHub

Spin Spin Spin