Searched refs:locking (Results 1 – 25 of 194) sorted by relevance
12345678
| /Linux-v5.10/Documentation/filesystems/ |
| D | mandatory-locking.rst | 13 0. Why you should avoid mandatory locking
32 1. What is mandatory locking?
35 Mandatory locking is kernel enforced file locking, as opposed to the more usual
36 cooperative file locking used to guarantee sequential access to files among
47 "advisory" locking scheme. However, the world isn't perfect, and there's
51 with a "mandatory" locking scheme, whereby the operating system kernel would
56 The System V mandatory locking scheme was intended to have as little impact as
58 as candidates for mandatory locking, and using the existing fcntl()/lockf()
64 the whole truth. System V locking is based on fcntl(). The granularity of
65 fcntl() is such that it allows the locking of byte ranges in files, in
[all …]
|
| D | locks.rst | 60 Mandatory locking, as described in
61 'Documentation/filesystems/mandatory-locking.rst' was prior to this release a
67 From this release of the kernel, mandatory locking can be turned on and off
69 The default is to disallow mandatory locking. The intention is that
70 mandatory locking only be enabled on a local filesystem as the specific need
|
| D | index.rst | 25 locking
26 directory-locking
32 mandatory-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.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.
|
| D | gfs2.rst | 17 GFS uses interchangeable inter-node locking mechanisms, the currently
24 - uses a distributed lock manager (dlm) for inter-node locking.
|
| /Linux-v5.10/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.10/tools/memory-model/Documentation/ |
| 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
48 year 1981, almost all kernel developers are very familiar with locking.
52 Please use the standard locking primitives provided by the kernel rather
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.
[all …]
|
| /Linux-v5.10/Documentation/locking/ |
| D | index.rst | 4 locking chapter
20 preempt-locking
|
| 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
62 locking error messages, inside curlies, with a total of 2 * n STATEs bits.
152 i.e., there can be any other locking sequence between the acquire-lock
168 The above rules are enforced for any locking sequence that occurs in the
192 Exception: Nested data dependencies leading to nested locking
202 An example of such an object hierarchy that results in "nested locking"
207 automatically detect this natural ordering, as the locking rule behind
[all …]
|
| 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
|
| 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.
|
| 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.
|
| 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.
|
| 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
|
| D | seqlock.rst | 207 2. Locking readers which will wait if a writer or another locking reader
208 is in progress. A locking reader in progress will also block a writer
210 exclusive. Unlike rwlock_t, only one locking reader can acquire it::
218 3. Conditional lockless reader (as in 1), or locking reader (as in 2),
224 full locking read and no retry loop is necessary::
|
| /Linux-v5.10/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.10/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.10/Documentation/kernel-hacking/ |
| D | index.rst | 11 locking
|
| /Linux-v5.10/Documentation/driver-api/soundwire/ |
| D | index.rst | 11 locking
|
| /Linux-v5.10/Documentation/pcmcia/ |
| D | index.rst | 12 locking
|
| /Linux-v5.10/Documentation/translations/it_IT/kernel-hacking/ |
| D | index.rst | 16 locking
|
| /Linux-v5.10/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.10/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.10/Documentation/virt/kvm/ |
| D | index.rst | 15 locking
|
12345678
