Home
last modified time | relevance | path

Searched refs:mutexes (Results 1 – 25 of 56) sorted by relevance

123

/third_party/ltp/testcases/realtime/func/pi-tests/
Dsbrk_mutex.c53 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/
Dlib.rs184 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/
Dthread_identity_test.cc108 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/
Dkeyed_mutex_submit.txt10 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,
Dkeyed_mutex_submit.adoc10 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/
Dcoverage.txt5 2 NO *Looking for indicators to judge if initialized mutexes
/third_party/ltp/testcases/open_posix_testsuite/conformance/interfaces/pthread_cancel/
Dcoverage.txt13 NOTE: In a lot of these test, I didn't make use of semaphores or mutexes, but
/third_party/rust/crates/bindgen/book/src/
Dnocopy.md22 * mutexes can't move in memory!
/third_party/ltp/testcases/realtime/
D00_Descriptions.txt141 - 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/
Dcustom.md93 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/
DREADME.md18 signal handler is limited to very few of them. To highlight, mutexes (or other
/third_party/mesa3d/docs/_extra/specs/
DMESA_multithread_makecurrent.spec74 mutexes.
/third_party/vk-gl-cts/external/vulkan-docs/src/appendices/
DVK_KHR_external_memory_capabilities.txt78 D3D11 surfaces must be synchronized using shared mutexes, and these
DVK_KHR_external_memory_capabilities.adoc78 D3D11 surfaces must be synchronized using shared mutexes, and these
/third_party/libunwind/
DTODO79 + use pthread-mutexes where necessary, atomic ops where possible
/third_party/ffmpeg/libavcodec/
Dpthread_frame.c711 #define DEFINE_OFFSET_ARRAY(type, name, mutexes, conds) \ argument
713 OFFSET_ARRAY mutexes, \
/third_party/libuv/docs/src/guide/
Dthreads.rst98 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.rst18 (also called :dfn:`mutexes` or :dfn:`binary semaphores`) are provided.
/third_party/ffmpeg/libavdevice/
Daudiotoolbox.m225 // init the mutexes for double-buffering
/third_party/musl/
DWHATSNEW309 - 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/
Devents3185 mutexes because in principal we don't support sending events to
/third_party/libuv/
DMakefile.am208 test/test-mutexes.c \
/third_party/skia/third_party/externals/oboe/docs/
DFullGuide.md442 - use mutexes or other synchronization primitives
489 This is because Oboe avoids using mutexes, which can cause thread preemption and glitches.
/third_party/lwip/
DUPGRADING196 binary semaphores instead of mutexes - as before)
/third_party/libwebsockets/READMEs/
DREADME.event-loops-intro.md41 It means that all mutexes and other synchronization and locking can be

123