| /third_party/boost/libs/thread/test/ |
| D | test_generic_locks.cpp | 221 void lock_n(boost::mutex* mutexes,unsigned count) in lock_n() argument
223 boost::lock(mutexes,mutexes+count); in lock_n()
226 mutexes[i].unlock(); in lock_n()
235 boost::mutex mutexes[num_mutexes]; in BOOST_AUTO_TEST_CASE() local
239 …boost::thread t(lock_five_mutexes_slowly,&mutexes[6],&mutexes[3],&mutexes[8],&mutexes[0],&mutexes[… in BOOST_AUTO_TEST_CASE()
242 boost::thread t2(lock_n,mutexes,num_mutexes); in BOOST_AUTO_TEST_CASE()
295 dummy_mutex mutexes[num_mutexes]; in BOOST_AUTO_TEST_CASE() local
297 boost::lock(mutexes,mutexes+num_mutexes); in BOOST_AUTO_TEST_CASE()
301 BOOST_CHECK(mutexes[i].is_locked); in BOOST_AUTO_TEST_CASE()
364 dummy_mutex mutexes[num_mutexes]; in BOOST_AUTO_TEST_CASE() local
[all …]
|
| /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/boost/libs/thread/doc/ |
| D | sync_tutorial.qbk | 11 …rg/web/20140531071228/http://home.roadrunner.com/~hinnant/mutexes/locking.html Handling mutexes in…
14 …ion Variable Rationale] adds rationale for the design decisions made for mutexes, locks and condit…
|
| D | synchronized_value_ref.qbk | 213 [[Effects:] [Copies the underlying value on a scope protected by the two mutexes. The mutex is not …
277 …protected by both mutex. Both mutex are acquired to avoid dead-lock. The mutexes are not swapped.]]
292 …protected by both mutex. Both mutex are acquired to avoid dead-lock. The mutexes are not swapped.]]
|
| D | synchronized_value.qbk | 99 …rwise you have the potential for deadlock. This is just the same as when acquiring any two mutexes.
118 …::tuple is to use the free synchronize function, which will lock all the mutexes associated to the…
|
| D | internal_locking.qbk | 87 …e difficult to describe synchronization by means of mutexes. Programs that make heavy use of mutex…
294 …tor is one example of a high-level concurrency abstraction that can be defined by means of mutexes.
|
| /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/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/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/boost/libs/outcome/doc/src/content/tutorial/advanced/hooks/ |
| D | keeping_state.md | 15 perhaps kept per-thread to avoid the need to keep mutexes.
|
| /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/boost/boost/asio/detail/impl/ |
| D | strand_executor_service.ipp | 62 // Select a mutex from the pool of shared mutexes.
|
| /third_party/boost/libs/asio/include/boost/asio/detail/impl/ |
| D | strand_executor_service.ipp | 62 // Select a mutex from the pool of shared mutexes.
|
| /third_party/boost/libs/beast/doc/qbk/08_design/ |
| D | 3_websocket_zaphoyd.qbk | 116 websocketpp uses mutexes to protect shared data from concurrent
117 access. In contrast, Beast does not use mutexes anywhere in its
127 costs associated with mutexes are incurred.
|
| /third_party/boost/libs/asio/doc/overview/ |
| D | strands.qbk | 13 mutexes).
|
| /third_party/mesa3d/docs/_extra/specs/ |
| D | MESA_multithread_makecurrent.spec | 74 mutexes.
|
| /third_party/libunwind/ |
| D | TODO | 79 + use pthread-mutexes where necessary, atomic ops where possible
|
| /third_party/boost/libs/lockfree/doc/ |
| D | lockfree.qbk | 61 Non-blocking data structures do not rely on locks and mutexes to ensure thread-safety. The synchron…
91 Apart from locks and mutexes (which we are not using in _lockfree_ anyway), there are three other a…
|
| /third_party/boost/libs/interprocess/doc/ |
| D | interprocess.qbk | 29 * Semaphores, mutexes, condition variables and upgradable mutex types to place
62 classes like mutexes, condition variables, etc... In some operating systems,
253 Examples of this are shared memory, named mutexes and named semaphores (for example,
271 named mutexes/conditions/semaphores) have kernel or filesystem persistency.
315 (mutexes, semaphores, etc...) between users, it's necessary to specify
327 changes (eg.: in Windows mutexes require `synchronize permissions`, but
1326 * Upgradable mutexes
1333 [section:mutexes Mutexes]
1358 * Recursive mutexes can be locked several times by the same thread. To fully unlock the
1361 * Non-recursive mutexes can't be locked several times by the same thread. If a mutex
[all …]
|
| /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/ffmpeg/libavcodec/ |
| D | pthread_frame.c | 711 #define DEFINE_OFFSET_ARRAY(type, name, mutexes, conds) \ argument
713 OFFSET_ARRAY mutexes, \
|
| /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/ffmpeg/libavdevice/ |
| D | audiotoolbox.m | 225 // init the mutexes for double-buffering
|