Searched refs:barrier (Results 1 – 4 of 4) sorted by relevance
51 pthread_cond_t barrier; variable226 pthread_cond_broadcast(&barrier); in manager_fn()229 pthread_cond_wait(&barrier, &funnel); in manager_fn()401 pthread_cond_init(&barrier, NULL); in main()
50 pthread_cond_t barrier; variable233 pthread_cond_broadcast(&barrier); in manager_fn()236 pthread_cond_wait(&barrier, &funnel); in manager_fn()374 pthread_cond_init(&barrier, NULL); in main()
108 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's150 `atomic_signal_fence()`. The barrier ordering argument is optional151 and defaults to the `acq_rel` compiler barrier (which prevents the152 compiler to reorder code in any direction around this barrier).154 `os_atomic_thread_fence(mem_order)` provides a memory barrier335 implicit compiler barrier, that can be used as a root for a chain of hardware371 * Using an acquire barrier would of course fix it but is quite expensive...387 * which properly pair with the release barrier in `publish`.
86 unsigned int barrier; /* bitmap barrier for CPU slop */ member