Searched refs:locking (Results 1 – 25 of 223) sorted by relevance
123456789
| /linux/kernel/locking/ |
| A D | .built-in.a.cmd | 1 …locking/built-in.a := echo >/dev/null; rm -f kernel/locking/built-in.a; /usr/bin/ccache /home/test…
|
| A D | .qspinlock.o.cmd | 1 …locking/qspinlock.o := /usr/bin/ccache /home/test/workspace/code/optee_3.16/build/../toolchains/aa…
3 source_kernel/locking/qspinlock.o := kernel/locking/qspinlock.c
5 deps_kernel/locking/qspinlock.o := \
830 kernel/locking/qspinlock_stat.h \
832 kernel/locking/lock_events.h \
833 kernel/locking/lock_events_list.h \
835 kernel/locking/mcs_spinlock.h \
839 kernel/locking/qspinlock.o: $(deps_kernel/locking/qspinlock.o)
841 $(deps_kernel/locking/qspinlock.o):
|
| A D | .rtmutex_api.o.cmd | 1 …locking/rtmutex_api.o := /usr/bin/ccache /home/test/workspace/code/optee_3.16/build/../toolchains/…
3 source_kernel/locking/rtmutex_api.o := kernel/locking/rtmutex_api.c
5 deps_kernel/locking/rtmutex_api.o := \
420 kernel/locking/rtmutex.c \
752 kernel/locking/rtmutex_common.h \
754 kernel/locking/rtmutex_api.o: $(deps_kernel/locking/rtmutex_api.o)
756 $(deps_kernel/locking/rtmutex_api.o):
|
| /linux/kernel/ |
| A D | built-in.a | 59 locking/mutex.o/
60 locking/semaphore.o/
61 locking/rwsem.o/
62 locking/percpu-rwsem.o/
63 locking/spinlock.o/
64 locking/osq_lock.o/
65 locking/qspinlock.o/
66 locking/rtmutex_api.o/
67 locking/qrwlock.o/
|
| /linux/tools/memory-model/Documentation/ |
| A D | simple.txt | 39 This approach is called "code locking".
41 Code locking can severely limit both performance and scalability, so it
47 One of the advantages of locking is that, in happy contrast with the
58 locking functions must carefully prevent both the CPU and the compiler
59 from moving code in either direction across the locking function.
86 Data locking
89 With code locking, we use single-threaded code execution to guarantee
104 As the number of buckets increases, data locking scales naturally.
131 Packaged primitives: Sequence locking
160 and "protect updates with locking".
[all …]
|
| /linux/fs/gfs2/ |
| A D | Kconfig | 21 the locking module below. Documentation and utilities for GFS2 can
28 bool "GFS2 DLM locking"
32 Multiple node locking module for GFS2
34 Most users of GFS2 will require this. It provides the locking
|
| /linux/Documentation/locking/ |
| A D | lockdep-design.rst | 1 Runtime locking correctness validator
14 respect to locking rules, even if the locks may have multiple (possibly
51 where the n STATEs are coded in kernel/locking/lockdep_states.h and as of
61 When locking rules are violated, these usage bits are presented in the
152 i.e., there can be any other locking sequence between the acquire-lock
192 Exception: Nested data dependencies leading to nested locking
207 automatically detect this natural ordering, as the locking rule behind
293 locking chains have to occur at least once (anytime, in any
300 This radically decreases the complexity of locking related QA of the
302 single-task locking dependencies in the kernel as possible, at least
[all …]
|
| A D | index.rst | 4 locking chapter
20 preempt-locking
|
| A D | preempt-locking.rst | 12 A preemptible kernel creates new locking issues. The issues are the same as
14 kernel model leverages existing SMP locking mechanisms. Thus, the kernel
15 requires explicit additional locking for very few additional situations.
32 First, since the data is per-CPU, it may not have explicit SMP locking, but
132 in doubt, rely on locking or explicit preemption disabling.
|
| A D | percpu-rw-semaphore.rst | 6 optimized for locking for reading.
14 instruction in the lock and unlock path. On the other hand, locking for
|
| A D | pi-futex.rst | 18 recursive locking, etc.
26 improve the statistical distribution of locking related application
54 to think about how to offer the option of a deterministic locking
62 problems as other user-space locking constructs). Fact is, pretty much
122 Documentation/locking/rt-mutex.rst.
|
| A D | locktorture.rst | 9 that runs torture tests on core kernel locking primitives. The kernel
76 Torture-framework (RCU + locking)
145 -only- be positive if there is a bug in the locking primitive's
167 were no locking failures, CPU-hotplug problems were detected.
|
| A D | seqlock.rst | 206 2. Locking readers which will wait if a writer or another locking reader
207 is in progress. A locking reader in progress will also block a writer
209 exclusive. Unlike rwlock_t, only one locking reader can acquire it::
217 3. Conditional lockless reader (as in 1), or locking reader (as in 2),
223 full locking read and no retry loop is necessary::
|
| A D | rt-mutex.rst | 7 (PTHREAD_PRIO_INHERIT). [See Documentation/locking/pi-futex.rst for more details
41 locking overhead when locking an uncontended mutex or unlocking a mutex
|
| A D | mutex-design.rst | 12 In the Linux kernel, mutexes refer to a particular locking primitive
27 and implemented in kernel/locking/mutex.c. These locks use an atomic variable
83 - Recursive locking/unlocking is not permitted.
152 locking primitive.
|
| /linux/tools/memory-model/ |
| A D | linux-kernel.bell | 56 flag ~empty Rcu-lock \ domain(rcu-rscs) as unbalanced-rcu-locking
57 flag ~empty Rcu-unlock \ range(rcu-rscs) as unbalanced-rcu-locking
72 flag ~empty Srcu-lock \ domain(srcu-rscs) as unbalanced-srcu-locking
73 flag ~empty Srcu-unlock \ range(srcu-rscs) as unbalanced-srcu-locking
|
| /linux/Documentation/filesystems/ |
| A D | locking.rst | 34 locking rules:
87 locking rules:
139 locking rules:
174 locking rules:
225 locking rules:
271 locking rules:
418 locking rules:
443 locking rules:
462 locking rules:
483 locking rules:
[all …]
|
| A D | index.rst | 25 locking
26 directory-locking
|
| A D | dlmfs.rst | 41 dlmfs for easy to setup and easy to use clustered locking in
69 system calls and presents a more traditional locking api.
74 locking.
140 For more information on the VMS distributed locking API.
|
| A D | gfs2.rst | 15 GFS2 uses interchangeable inter-node locking mechanisms, the currently
22 - uses the distributed lock manager (dlm) for inter-node locking.
|
| A D | files.rst | 7 This document describes how locking for files (struct file)
22 the reference counting is similar, but the locking is
36 appear atomic. Here are the locking rules for
|
| /linux/Documentation/gpu/ |
| A D | introduction.rst | 34 locking requirements for functions aren't documented in the kerneldoc.
35 Instead locking should be check at runtime using e.g.
38 that runtime checks do need to be updated when the locking rules change,
40 the locking rules should be explained in the relevant structures: Either
|
| /linux/Documentation/sound/cards/ |
| A D | img-spdif-in.rst | 43 This control is used to modify the locking/jitter rejection characteristics
44 of the block. Larger values increase the locking range, but reduce jitter
|
| /linux/Documentation/process/ |
| A D | volatile-considered-harmful.rst | 35 If all the code follows the locking rules, the value of shared_data cannot
45 If shared_data were declared volatile, the locking would still be
49 volatile. When dealing with shared data, proper locking makes volatile
87 locking. So jiffies can be volatile, but the addition of other
|
| /linux/Documentation/kernel-hacking/ |
| A D | index.rst | 11 locking
|
Completed in 31 milliseconds
123456789