Searched full:mutexes (Results 1 – 22 of 22) sorted by relevance
| /Documentation/locking/ |
| D | mutex-design.rst | 9 What are mutexes?
12 In the Linux kernel, mutexes refer to a particular locking primitive
15 or similar theoretical text books. Mutexes are sleeping locks which
26 Mutexes are represented by 'struct mutex', defined in include/linux/mutex.h
69 While formally kernel mutexes are sleepable locks, it is path (ii) that
87 - Held mutexes must not be reinitialized.
88 - Mutexes may not be used in hardware or software interrupt
95 - Uses symbolic names of mutexes, whenever they are printed
104 Mutexes - and most other sleeping locks like rwsems - do not provide an
165 When to use mutexes
[all …]
|
| D | rt-mutex.rst | 5 RT-mutexes with priority inheritance are used to support PI-futexes,
16 RT-mutexes extend the semantics of simple mutexes by the priority
27 mutexes which protect shared resources. Priority inheritance is not a
40 RT-mutexes are optimized for fastpath operations and have no internal
|
| D | ww-mutex-design.rst | 5 Please read mutex-design.rst first, as it applies to wait/wound mutexes too.
7 Motivation for WW-Mutexes
60 Compared to normal mutexes two additional concepts/objects show up in the lock
61 interface for w/w mutexes:
70 W/w class: In contrast to normal mutexes the lock class needs to be explicit for
71 w/w mutexes, since it is required to initialize the acquire context. The lock
238 mutexes are a natural fit for such a case for two reasons:
340 increase in code size if wait/wound mutexes are not used.
373 - Attempting to lock more mutexes after ww_acquire_done.
375 unlocking all mutexes.
[all …]
|
| D | rt-mutex-design.rst | 120 - The highest priority process waiting on one of the mutexes
131 The PI chain is a list of processes and mutexes that may cause priority
139 Mutexes: L1, L2, L3, L4
177 have multiple chains merge at mutexes. If we add another process G that is
209 a tree of all top waiters of the mutexes that are owned by the process.
211 blocked on mutexes owned by the process.
229 the nesting of mutexes. Let's look at the example where we have 3 mutexes,
293 Now since mutexes can be defined by user-land applications, we don't want a DOS
294 type of application that nests large amounts of mutexes to create a large
318 mutexes short.
[all …]
|
| D | pi-futex.rst | 64 locks (such as futex-based pthread mutexes) is priority inheritance:
79 mutexes involves no kernel work at all - they behave quite similarly to
82 futexes.) Userspace uses atomic ops to lock/unlock these mutexes without
115 possible anyway, due to existing ABI properties of pthread mutexes.]
|
| D | robust-futexes.rst | 42 There is a big conceptual problem with futex based mutexes though: it is
122 mechanism, which fully enables robust mutexes.
133 - no registration of individual locks is needed: robust mutexes don't
134 need any extra per-lock syscalls. Robust mutexes thus become a very
137 mutexes are just as fast.
158 [which it currently does for !pshared robust mutexes], and that took 256
|
| D | locktypes.rst | 101 RT-mutexes are mutexes with support for priority inheritance (PI).
110 and rwlock_t to be implemented via RT-mutexes.
120 as mutexes and completions.
|
| D | lockdep-design.rst | 111 Unused locks (e.g., mutexes) cannot be part of the cause of an error.
|
| /Documentation/devicetree/bindings/hwlock/ |
| D | qcom-hwspinlock.yaml | 13 The hardware block provides mutexes utilized between different processors on
|
| /Documentation/userspace-api/ |
| D | futex2.rst | 10 performant synchronization mechanisms, such as mutexes, semaphores and
|
| /Documentation/driver-api/media/ |
| D | dtv-demux.rst | 39 addressed, e.g. by protecting parts of code with mutexes.
|
| /Documentation/livepatch/ |
| D | callbacks.rst | 18 mutexes/spinlocks, or even stop_machine(), to avoid concurrency issues.
|
| /Documentation/process/ |
| D | volatile-considered-harmful.rst | 22 safe (spinlocks, mutexes, memory barriers, etc.) are designed to prevent
|
| /Documentation/scheduler/ |
| D | completion.rst | 182 most cases you probably don't want to call this with held mutexes.
|
| /Documentation/kernel-hacking/ |
| D | locking.rst | 101 Two Main Types of Kernel Locks: Spinlocks and Mutexes
138 Mutexes still exist, because they are required for synchronization
879 (spinlocks, rwlocks and mutexes are not recursive in Linux). This is
1052 Both spinlocks and mutexes have read/write variants: ``rwlock_t`` and
|
| /Documentation/virt/kvm/ |
| D | locking.rst | 10 The acquisition orders for mutexes are as follows:
|
| /Documentation/trace/ |
| D | kprobes.rst | 574 Kprobes does not use mutexes or allocate memory except during
|
| /Documentation/RCU/Design/Expedited-Grace-Periods/ |
| D | Expedited-Grace-Periods.rst | 513 expedited grace period are awakened. A pair of mutexes are used to allow
|
| /Documentation/sound/kernel-api/ |
| D | writing-an-alsa-driver.rst | 1874 mutexes or any schedule-related functions are not available in the
2193 usually avoided via spin-locks, mutexes or semaphores. In general, if a
2198 mutexes or semaphores instead.
2209 mutexes can sleep, and hence they cannot be used inside the atomic
|
| /Documentation/networking/dsa/ |
| D | dsa.rst | 629 interrupts, mutexes, locks, etc. This function is also expected to properly
|
| /Documentation/ |
| D | memory-barriers.txt | 2000 (*) mutexes
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 3175 of preemption. Note that non-realtime mutexes
|