/third_party/ltp/testcases/realtime/func/pi-tests/ |
D | sbrk_mutex.c | 53 static pthread_mutex_t *mutexes[NUM_MUTEXES]; variable 83 pthread_mutex_unlock(mutexes[i - NUM_CONCURRENT_LOCKS]); in worker_thread() 87 pthread_mutex_lock(mutexes[i]); in worker_thread() 123 if (!(mutexes[m] = malloc(sizeof(pthread_mutex_t)))) { in main() 126 if ((ret = pthread_mutex_init(mutexes[m], &mutexattr))) { in main() 142 if (mutexes[m]) { in main() 143 if ((ret = pthread_mutex_destroy(mutexes[m]))) in main() 145 free(mutexes[m]); in main()
|
/third_party/rust/crates/rust-openssl/openssl-sys/src/ |
D | lib.rs | 184 let mut mutexes = Box::new(Vec::new()); in init() localVariable 186 mutexes.push(Mutex::new(())); in init() 188 MUTEXES = mem::transmute(mutexes); in init()
|
/third_party/skia/third_party/externals/abseil-cpp/absl/base/internal/ |
D | thread_identity_test.cc | 108 Mutex mutexes[kNumMutexes]; in TEST() local 115 MutexLock lock(&mutexes[m]); in TEST()
|
/third_party/vk-gl-cts/external/vulkan-docs/src/chapters/VK_NV_win32_keyed_mutex/ |
D | keyed_mutex_submit.txt | 10 Keyed mutexes are a property of a properly created shareable Direct3D 11 15 To acquire keyed mutexes before submitted work and/or release them after,
|
D | keyed_mutex_submit.adoc | 10 Keyed mutexes are a property of a properly created shareable Direct3D 11 15 To acquire keyed mutexes before submitted work and/or release them after,
|
/third_party/ltp/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutexattr_init/ |
D | coverage.txt | 5 2 NO *Looking for indicators to judge if initialized mutexes
|
/third_party/ltp/testcases/open_posix_testsuite/conformance/interfaces/pthread_cancel/ |
D | coverage.txt | 13 NOTE: In a lot of these test, I didn't make use of semaphores or mutexes, but
|
/third_party/rust/crates/bindgen/book/src/ |
D | nocopy.md | 22 * mutexes can't move in memory!
|
/third_party/ltp/testcases/realtime/ |
D | 00_Descriptions.txt | 141 - Uses NUM_THREADS to walk through an array of malloc'd pthread mutexes. 149 with different priorities, all fight for holding mutexes. Threads sleep and 236 several slave threads, all fighting for mutexes.
|
/third_party/icu/docs/userguide/dev/sync/ |
D | custom.md | 93 Example ICU configure with user mutexes specified: 110 This implementation uses C++11 language mutexes and atomics. These make for a
|
/third_party/rust/crates/signal-hook/ |
D | README.md | 18 signal handler is limited to very few of them. To highlight, mutexes (or other
|
/third_party/mesa3d/docs/_extra/specs/ |
D | MESA_multithread_makecurrent.spec | 74 mutexes.
|
/third_party/vk-gl-cts/external/vulkan-docs/src/appendices/ |
D | VK_KHR_external_memory_capabilities.txt | 78 D3D11 surfaces must be synchronized using shared mutexes, and these
|
D | VK_KHR_external_memory_capabilities.adoc | 78 D3D11 surfaces must be synchronized using shared mutexes, and these
|
/third_party/libunwind/ |
D | TODO | 79 + use pthread-mutexes where necessary, atomic ops where possible
|
/third_party/ffmpeg/libavcodec/ |
D | pthread_frame.c | 711 #define DEFINE_OFFSET_ARRAY(type, name, mutexes, conds) \ argument 713 OFFSET_ARRAY mutexes, \
|
/third_party/libuv/docs/src/guide/ |
D | threads.rst | 98 Recursive mutexes are supported, but you should not rely on them. Also, they 362 mutexes and rwlocks **DO NOT** work inside a signal handler, whereas
|
/third_party/python/Doc/library/ |
D | _thread.rst | 18 (also called :dfn:`mutexes` or :dfn:`binary semaphores`) are provided.
|
/third_party/ffmpeg/libavdevice/ |
D | audiotoolbox.m | 225 // init the mutexes for double-buffering
|
/third_party/musl/ |
D | WHATSNEW | 309 - destruction/unmapping race conditions in semaphores, mutexes, rwlocks 372 - recursive mutexes are now fully reentrant 386 - lock count corruption with robust recursive mutexes on owner death 706 - extremely rare/obscure race condition with robust mutexes 1351 - corruption of cond var mutex state when switching mutexes 1353 - false ownership of orphaned mutexes due to tid reuse 1354 - possible failure-to-wake for robust mutexes on owner death 1489 - failure to process robust mutexes on detached-thread exit 2044 - priority-inheritance mutexes
|
/third_party/gstreamer/gstreamer/docs/random/wtay/ |
D | events3 | 185 mutexes because in principal we don't support sending events to
|
/third_party/libuv/ |
D | Makefile.am | 208 test/test-mutexes.c \
|
/third_party/skia/third_party/externals/oboe/docs/ |
D | FullGuide.md | 442 - use mutexes or other synchronization primitives 489 This is because Oboe avoids using mutexes, which can cause thread preemption and glitches.
|
/third_party/lwip/ |
D | UPGRADING | 196 binary semaphores instead of mutexes - as before)
|
/third_party/libwebsockets/READMEs/ |
D | README.event-loops-intro.md | 41 It means that all mutexes and other synchronization and locking can be
|