Searched refs:semaphores (Results 1 – 24 of 24) sorted by relevance
| /Linux-v5.15/Documentation/locking/ |
| D | percpu-rw-semaphore.rst | 2 Percpu rw semaphores
5 Percpu rw semaphores is a new read-write semaphore design that is
8 The problem with traditional read-write semaphores is that when multiple
|
| 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
|
| 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-v5.15/drivers/gpu/drm/radeon/ |
| D | radeon_sync.c | 46 sync->semaphores[i] = NULL; in radeon_sync_create()
169 sync->semaphores[count++] = semaphore; in radeon_sync_rings()
219 radeon_semaphore_free(rdev, &sync->semaphores[i], fence); in radeon_sync_free()
|
| D | radeon.h | 610 struct radeon_semaphore *semaphores[RADEON_NUM_SYNCS]; member
|
| /Linux-v5.15/Documentation/devicetree/bindings/mailbox/ |
| D | nvidia,tegra186-hsp.txt | 9 The features that HSP supported are shared mailboxes, shared semaphores,
10 arbitrated semaphores and doorbells.
|
| /Linux-v5.15/Documentation/translations/zh_CN/infiniband/ |
| D | core_locking.rst | 109 不能持有任何可能导致死锁的semaphores。
|
| /Linux-v5.15/drivers/gpu/drm/i915/ |
| D | i915_scheduler_types.h | 69 intel_engine_mask_t semaphores; member
|
| D | i915_request.c | 608 if (request->sched.semaphores && in __i915_request_submit()
610 engine->saturated |= request->sched.semaphores; in __i915_request_submit()
687 if (request->sched.semaphores && __i915_request_has_started(request)) in __i915_request_unsubmit()
688 request->sched.semaphores = 0; in __i915_request_unsubmit()
1094 return rq->sched.semaphores | READ_ONCE(rq->engine->saturated); in already_busywaiting()
1185 to->sched.semaphores |= mask; in emit_semaphore_wait()
|
| D | Kconfig.profile | 114 interact with each other via userspace semaphores. Each context
|
| D | i915_scheduler.c | 308 node->semaphores = 0; in i915_sched_node_reinit()
|
| /Linux-v5.15/drivers/media/pci/cx18/ |
| D | cx18-scb.h | 231 u32 semaphores[8]; /* Semaphores */ member
|
| /Linux-v5.15/Documentation/infiniband/ |
| D | core_locking.rst | 108 semaphores that could cause deadlock if a consumer calls back into
|
| /Linux-v5.15/Documentation/scsi/ |
| D | ChangeLog.ips | 26 4.80.14 - Take all semaphores off stack
|
| /Linux-v5.15/Documentation/RCU/ |
| D | rcuref.rst | 17 reader/writer spinlocks or semaphores are straightforward:
|
| D | whatisRCU.rst | 468 - Use some solid scheme (such as locks or semaphores) to
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | journalling.rst | 88 jbd2_journal_stop() as if they were semaphores and include them in
|
| /Linux-v5.15/Documentation/scheduler/ |
| D | completion.rst | 14 misuse of locks/semaphores and busy-loops. Any time you think of using
|
| /Linux-v5.15/arch/arc/ |
| D | Kconfig | 195 hardware semaphores, shared memory,....
|
| /Linux-v5.15/Documentation/PCI/ |
| D | pci-error-recovery.rst | 135 to complete; it can take semaphores, schedule, etc... everything but
|
| /Linux-v5.15/Documentation/ |
| D | memory-barriers.txt | 1973 (*) semaphores
1974 (*) R/W semaphores
2077 Locks and semaphores may not provide any guarantee of ordering on UP compiled
|
| /Linux-v5.15/Documentation/sound/kernel-api/ |
| D | writing-an-alsa-driver.rst | 2283 usually avoided via spin-locks, mutexes or semaphores. In general, if a
2288 mutexes or semaphores instead.
|
| /Linux-v5.15/Documentation/sound/ |
| D | alsa-configuration.rst | 1289 Enable workaround for hardware with buggy semaphores (e.g. on some
|
| /Linux-v5.15/ |
| D | CREDITS | 3243 D: shm fs, SYSV semaphores, af_unix
|
