| /linux/tools/testing/selftests/powerpc/dscr/ |
| H A D | dscr_explicit_test.c | 55 sem_t semaphores[2]; in dscr_explicit_lockstep_test() local
56 sem_t *prev = &semaphores[1]; /* reversed prev/next than for the other thread */ in dscr_explicit_lockstep_test()
57 sem_t *next = &semaphores[0]; in dscr_explicit_lockstep_test()
68 FAIL_IF(pthread_create(&thread, NULL, dscr_explicit_lockstep_thread, (void *)semaphores)); in dscr_explicit_lockstep_test()
|
| /linux/drivers/gpu/drm/radeon/ |
| H A D | radeon_sync.c | 46 sync->semaphores[i] = NULL; in radeon_sync_create()
153 sync->semaphores[count++] = semaphore; in radeon_sync_rings()
203 radeon_semaphore_free(rdev, &sync->semaphores[i], fence); in radeon_sync_free()
|
| H A D | radeon.h | 571 struct radeon_semaphore *semaphores[RADEON_NUM_SYNCS]; member
|
| /linux/Documentation/translations/zh_CN/locking/ |
| H A D | mutex-design.rst | 27 排斥”。互斥锁是一种睡眠锁，它的行为类似于二进制信号量（semaphores），在
72 改善一些工作负载的性能。注意，这种技术也被用于读写信号量（rw-semaphores）。
|
| /linux/Documentation/translations/zh_CN/infiniband/ |
| H A D | core_locking.rst | 109 不能持有任何可能导致死锁的semaphores。
|
| /linux/drivers/gpu/drm/i915/ |
| H A D | i915_scheduler_types.h | 69 intel_engine_mask_t semaphores; member
|
| H A D | i915_scheduler.c | 308 node->semaphores = 0; in i915_sched_node_reinit()
|
| H A D | Kconfig.profile | 132 interact with each other via userspace semaphores. Each context
|
| /linux/Documentation/locking/ |
| H A D | locktypes.rst | 89 The aforementioned lock types except semaphores have strict owner
122 semaphores and PREEMPT_RT
126 semaphores have no concept of owners, thus preventing PREEMPT_RT from
127 providing priority inheritance for semaphores. After all, an unknown
128 owner cannot be boosted. As a consequence, blocking on semaphores can
|
| H A D | mutex-design.rst | 16 behave similarly to binary semaphores, and were introduced in 2006[1]
73 number of workloads. Note that this technique is also used for rw-semaphores.
|
| /linux/drivers/media/pci/cx18/ |
| H A D | cx18-scb.h | 231 u32 semaphores[8]; /* Semaphores */ member
|
| /linux/Documentation/userspace-api/ |
| H A D | futex2.rst | 10 performant synchronization mechanisms, such as mutexes, semaphores and
|
| /linux/Documentation/infiniband/ |
| H A D | core_locking.rst | 108 semaphores that could cause deadlock if a consumer calls back into
|
| /linux/Documentation/scsi/ |
| H A D | ChangeLog.ips | 26 4.80.14 - Take all semaphores off stack
|
| /linux/Documentation/RCU/ |
| H A D | rcuref.rst | 17 reader/writer spinlocks or semaphores are straightforward:
|
| H A D | whatisRCU.rst | 505 - Use some solid design (such as locks or semaphores) to
|
| /linux/Documentation/filesystems/ |
| H A D | journalling.rst | 88 jbd2_journal_stop() as if they were semaphores and include them in
|
| /linux/Documentation/scheduler/ |
| H A D | completion.rst | 14 misuse of locks/semaphores and busy-loops. Any time you think of using
|
| /linux/arch/arc/ |
| H A D | Kconfig | 199 hardware semaphores, shared memory,....
|
| /linux/Documentation/PCI/ |
| H A D | pci-error-recovery.rst | 136 to complete; it can take semaphores, schedule, etc... everything but
|
| /linux/Documentation/ |
| H A D | memory-barriers.txt | 2001 (*) semaphores
2002 (*) R/W semaphores
2105 Locks and semaphores may not provide any guarantee of ordering on UP compiled
|
| /linux/Documentation/mm/ |
| H A D | process_addrs.rst | 131 All of these locks behave as read/write semaphores in practice, so you can
|
| /linux/Documentation/sound/kernel-api/ |
| H A D | writing-an-alsa-driver.rst | 2193 usually avoided via spin-locks, mutexes or semaphores. In general, if a
2198 mutexes or semaphores instead.
|
| /linux/Documentation/sound/ |
| H A D | alsa-configuration.rst | 1315 Enable workaround for hardware with buggy semaphores (e.g. on some
|
| /linux/ |
| H A D | CREDITS | 3419 D: shm fs, SYSV semaphores, af_unix
|