Searched refs:locking (Results 1 – 25 of 181) sorted by relevance
12345678
| /Linux-v5.4/Documentation/filesystems/ |
| D | mandatory-locking.txt | 8 0. Why you should avoid mandatory locking
27 1. What is mandatory locking?
30 Mandatory locking is kernel enforced file locking, as opposed to the more usual
31 cooperative file locking used to guarantee sequential access to files among
42 "advisory" locking scheme. However, the world isn't perfect, and there's
46 with a "mandatory" locking scheme, whereby the operating system kernel would
51 The System V mandatory locking scheme was intended to have as little impact as
53 as candidates for mandatory locking, and using the existing fcntl()/lockf()
57 the whole truth. System V locking is based on fcntl(). The granularity of
58 fcntl() is such that it allows the locking of byte ranges in files, in addition
[all …]
|
| D | locks.txt | 56 Mandatory locking, as described in
57 'Documentation/filesystems/mandatory-locking.txt' was prior to this release a
63 From this release of the kernel, mandatory locking can be turned on and off
65 The default is to disallow mandatory locking. The intention is that
66 mandatory locking only be enabled on a local filesystem as the specific need
|
| D | index.rst | 23 locking
24 directory-locking
|
| D | locking.rst | 5 The text below describes the locking rules for VFS-related methods.
7 prototypes or locking protocols - update this file. And update the relevant
34 locking rules:
84 locking rules:
117 See Documentation/filesystems/directory-locking.rst for more detailed discussion
118 of the locking scheme for directory operations.
133 locking rules:
168 locking rules:
204 writes to quota files with quotas on). For other details about locking
219 locking rules:
[all …]
|
| D | dlmfs.txt | 36 dlmfs for easy to setup and easy to use clustered locking in
64 system calls and presents a more traditional locking api.
69 locking.
130 For more information on the VMS distributed locking API.
|
| D | gfs2.txt | 14 GFS uses interchangeable inter-node locking mechanisms, the currently
19 lock_dlm -- uses a distributed lock manager (dlm) for inter-node locking
|
| D | files.txt | 4 This document describes how locking for files (struct file)
19 the reference counting is similar, but the locking is
33 appear atomic. Here are the locking rules for
|
| /Linux-v5.4/Documentation/locking/ |
| D | lockdep-design.rst | 1 Runtime locking correctness validator
14 respect to locking rules, even if the locks may have multiple (possibly
50 where the n STATEs are coded in kernel/locking/lockdep_states.h and as of
58 When locking rules are violated, these usage bits are presented in the
59 locking error messages, inside curlies, with a total of 2 * n STATEs bits.
149 i.e., there can be any other locking sequence between the acquire-lock
165 The above rules are enforced for any locking sequence that occurs in the
189 Exception: Nested data dependencies leading to nested locking
199 An example of such an object hierarchy that results in "nested locking"
204 automatically detect this natural ordering, as the locking rule behind
[all …]
|
| D | locktorture.rst | 9 that runs torture tests on core kernel locking primitives. The kernel
76 Torture-framework (RCU + locking)
146 -only- be positive if there is a bug in the locking primitive's
168 were no locking failures, CPU-hotplug problems were detected.
|
| D | index.rst | 4 locking chapter
|
| 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-v5.4/fs/gfs2/ |
| 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-v5.4/tools/memory-model/ |
| 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-v5.4/net/ax25/ |
| D | TODO | 15 Implement proper socket locking in netrom and rose.
17 Check socket locking when ax25_rcv is sending to raw sockets. In particular
|
| /Linux-v5.4/Documentation/ |
| D | percpu-rw-semaphore.txt | 6 optimized for locking for reading.
14 instruction in the lock and unlock path. On the other hand, locking for
|
| D | preempt-locking.txt | 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.
|
| D | pi-futex.txt | 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.
|
| /Linux-v5.4/Documentation/kernel-hacking/ |
| D | index.rst | 11 locking
|
| /Linux-v5.4/Documentation/driver-api/soundwire/ |
| D | index.rst | 11 locking
|
| /Linux-v5.4/Documentation/pcmcia/ |
| D | index.rst | 12 locking
|
| /Linux-v5.4/Documentation/translations/it_IT/kernel-hacking/ |
| D | index.rst | 16 locking
|
| /Linux-v5.4/Documentation/sound/cards/ |
| 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-v5.4/Documentation/gpu/ |
| 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-v5.4/drivers/thermal/ti-soc-thermal/ |
| D | TODO | 7 - Revisit need for locking
|
| /Linux-v5.4/Documentation/process/ |
| 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
|
12345678
