Home
last modified time | relevance | path

Searched refs:barrier (Results 1 – 5 of 5) sorted by relevance

/xnu-10002.1.13/tools/tests/affinity/
H A Dpool.c50 pthread_cond_t barrier; variable
233 pthread_cond_broadcast(&barrier); in manager_fn()
236 pthread_cond_wait(&barrier, &funnel); in manager_fn()
374 pthread_cond_init(&barrier, NULL); in main()
H A Dsets.c51 pthread_cond_t barrier; variable
226 pthread_cond_broadcast(&barrier); in manager_fn()
229 pthread_cond_wait(&barrier, &funnel); in manager_fn()
401 pthread_cond_init(&barrier, NULL); in main()
/xnu-10002.1.13/doc/
H A Datomics.md108 or a compiler barrier ordering `compiler_acquire`, `compiler_release`,
148 `os_compiler_barrier(mem_order?)` provides a compiler barrier,
149 with an optional barrier ordering. It is implemented with C11's
150 `atomic_signal_fence()`. The barrier ordering argument is optional
151 and defaults to the `acq_rel` compiler barrier (which prevents the
152 compiler to reorder code in any direction around this barrier).
154 `os_atomic_thread_fence(mem_order)` provides a memory barrier
335 implicit compiler barrier, that can be used as a root for a chain of hardware
371 * Using an acquire barrier would of course fix it but is quite expensive...
387 * which properly pair with the release barrier in `publish`.
H A Drecount.md97 …t once (thread, task, and processor), only the last update has a release barrier to publish the wr…
/xnu-10002.1.13/osfmk/i386/
H A Diopb.h86 unsigned int barrier; /* bitmap barrier for CPU slop */ member