<feed xmlns='http://www.w3.org/2005/Atom'>
<title>glibc/benchtests/pthread_once-inputs, branch master</title>
<subtitle>Fork of glibc for development</subtitle>
<id>https://git.zx2c4.com/glibc/atom/benchtests/pthread_once-inputs?h=master</id>
<link rel='self' href='https://git.zx2c4.com/glibc/atom/benchtests/pthread_once-inputs?h=master'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/'/>
<updated>2014-04-10T19:22:28Z</updated>
<entry>
<title>benchtests: Add pthread_once common-case test.</title>
<updated>2014-04-10T19:22:28Z</updated>
<author>
<name>Torvald Riegel</name>
<email>triegel@redhat.com</email>
</author>
<published>2013-10-08T11:17:01Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=6a5d6ea128153f5a00d8c80f15f76004006767da'/>
<id>urn:sha1:6a5d6ea128153f5a00d8c80f15f76004006767da</id>
<content type='text'>
We have a single thread that runs a no-op initialization once and then
repeatedly runs checks of the initialization (i.e., an acquire load and
conditional jump) in a tight loop.  This gives us, on average, the
best-case latency of pthread_once (the initialization is the
exactly-once slow path, and we're not looking at initialization-related
synchronization overheads in this case).
</content>
</entry>
</feed>
