diff --git a/tests/7158b1cdd50c.html b/tests/7158b1cdd50c.html index a9b2b60..1e0f305 100644 --- a/tests/7158b1cdd50c.html +++ b/tests/7158b1cdd50c.html @@ -150,7 +150,7 @@ rel="noreferrer"> Open post in medium.com .gist_file { background-color:#ffffff; }
}
- See gist on GitHub + 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.

@@ -178,7 +178,7 @@ rel="noreferrer"> Open post in medium.com .gist_file { background-color:#ffffff; }
}
- See gist on GitHub + See gist on GitHub

Spin Spin Spin