Searched full:locking (Results 1 – 25 of 1733) sorted by relevance
12345678910>>...70
3 * lib/locking-selftest.c5 * Testsuite for various locking APIs: spinlocks, rwlocks,309 #include "locking-selftest-spin.h"311 #include "locking-selftest-wlock.h"313 #include "locking-selftest-rlock.h"315 #include "locking-selftest-mutex.h"317 #include "locking-selftest-wsem.h"319 #include "locking-selftest-rsem.h"323 #include "locking-selftest-rtmutex.h"330 * Special-case for read-locking, they are[all …]
39 This approach is called "code locking".41 Code locking can severely limit both performance and scalability, so it47 One of the advantages of locking is that, in happy contrast with the48 year 1981, almost all kernel developers are very familiar with locking.52 Please use the standard locking primitives provided by the kernel rather58 locking functions must carefully prevent both the CPU and the compiler59 from moving code in either direction across the locking function.86 Data locking89 With code locking, we use single-threaded code execution to guarantee104 As the number of buckets increases, data locking scales naturally.[all …]
1 Locking4 Locking is well-known and the common use cases are straightforward: Any13 Locking and Prior Accesses16 The basic rule of locking is worth repeating:50 Locking and Subsequent Accesses82 locking basic rule extend across multiple acquisitions of a given lock86 Double-Checked Locking90 double-checked locking work correctly, This litmus test illustrates93 /* See Documentation/litmus-tests/locking/DCL-broken.litmus. */118 /* See Documentation/litmus-tests/locking/DCL-fixed.litmus. */[all …]
23 * Locking events for PV qspinlock.39 * Locking events for qspinlock44 LOCK_EVENT(lock_pending) /* # of locking ops via pending code */45 LOCK_EVENT(lock_slowpath) /* # of locking ops via MCS lock queue */46 LOCK_EVENT(lock_use_node2) /* # of locking ops that use 2nd percpu node */47 LOCK_EVENT(lock_use_node3) /* # of locking ops that use 3rd percpu node */48 LOCK_EVENT(lock_use_node4) /* # of locking ops that use 4th percpu node */49 LOCK_EVENT(lock_no_node) /* # of locking ops w/o using percpu node */53 * Locking events for rwsem
2 Directory Locking6 Locking scheme used for directory operations is based on two16 1) read access. Locking rules: caller locks directory we are accessing.19 2) object creation. Locking rules: same as above, but the lock is taken22 3) object removal. Locking rules: caller locks parent, finds victim,25 4) rename() that is _not_ cross-directory. Locking rules: caller locks the30 NB: we might get away with locking the source (and target in exchange33 5) link creation. Locking rules:42 6) cross-directory rename. The trickiest in the whole bunch. Locking59 All ->i_rwsem are taken exclusive. Again, we might get away with locking[all …]
41 dlmfs for easy to setup and easy to use clustered locking in64 Locking chapter69 system calls and presents a more traditional locking api.74 locking.94 domain directory. Locking against them is done via the open(2) system113 Open Flag Resulting Locking Behavior140 For more information on the VMS distributed locking API.
2 Locking chapter5 The text below describes the locking rules for VFS-related methods.7 prototypes or locking protocols - update this file. And update the relevant34 locking rules:90 locking rules:127 See Documentation/filesystems/directory-locking.rst for more detailed discussion128 of the locking scheme for directory operations.144 locking rules:178 locking rules:213 writes to quota files with quotas on). For other details about locking[all …]
210 * Locking note: This function must be called with the device lock held.211 * Locking is not handled inside the function. Callers should ensure they235 * Locking note: This function must be called with the device lock held.236 * Locking is not handled inside the function. Callers should ensure they260 * Locking note: This function must be called with the device lock held.261 * Locking is not handled inside the function. Callers should ensure they285 * Locking note: This function must be called with the device lock held.286 * Locking is not handled inside the function. Callers should ensure they319 * Locking note: This function must be called with the device lock held.320 * Locking is not handled inside the function. Callers should ensure they[all …]
1 Runtime locking correctness validator14 respect to locking rules, even if the locks may have multiple (possibly51 where the n STATEs are coded in kernel/locking/lockdep_states.h and as of61 When locking rules are violated, these usage bits are presented in the62 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-lock168 The above rules are enforced for any locking sequence that occurs in the192 Exception: Nested data dependencies leading to nested locking202 An example of such an object hierarchy that results in "nested locking"207 automatically detect this natural ordering, as the locking rule behind[all …]
2 Proper Locking Under a Preemptible Kernel: Keeping Kernel Code Preempt-Safe12 A preemptible kernel creates new locking issues. The issues are the same as14 kernel model leverages existing SMP locking mechanisms. Thus, the kernel15 requires explicit additional locking for very few additional situations.32 First, since the data is per-CPU, it may not have explicit SMP locking, but132 in doubt, rely on locking or explicit preemption disabling.
6 optimized for locking for reading.13 Locking for reading is very fast, it uses RCU and it avoids any atomic14 instruction in the lock and unlock path. On the other hand, locking for
18 recursive locking, etc.26 improve the statistical distribution of locking related application54 to think about how to offer the option of a deterministic locking62 problems as other user-space locking constructs). Fact is, pretty much122 Documentation/locking/rt-mutex.rst.
30 * Note about locking: There is no locking required until only one reader251 * a spinlock for locking253 * @lock: spinlock to be used for locking267 * using a spinlock for locking, doesn't disable interrupts269 * @lock: spinlock to be used for locking403 * writer, you don't need extra locking to use these macro.440 * writer, you don't need extra locking to use these macro.479 * writer, you don't need extra locking to use these macro.517 * writer, you don't need extra locking to use these macro.532 * kfifo_in_spinlocked - put data into the fifo using a spinlock for locking[all …]
9 * See Documentation/locking/seqlock.rst55 * locking primitives, use a sequence counter with associated lock62 * See Documentation/locking/seqlock.rst131 * See Documentation/locking/seqlock.rst148 * sleeping locks. See Documentation/locking/locktypes.rst500 * See Documentation/locking/lockdep-design.rst795 * - Documentation/locking/seqlock.rst996 * read_seqlock_excl() - begin a seqlock_t locking reader section999 * read_seqlock_excl opens a seqlock_t locking reader critical section. A1000 * locking reader exclusively locks out *both* other writers *and* other[all …]
48 * Locking: none.67 * Locking: @port->lock taken.87 * Locking: @port->lock taken.99 * Locking: @port->lock taken.107 * Locking: @port->lock taken.118 * Locking: serialized with @unthrottle() and termios modification by the129 * Locking: serialized with @throttle() and termios modification by the142 * Locking: none.149 * Locking: @port->lock taken.157 * Locking: @port->lock taken.[all …]
100 check_err $? "Ping did not work before locking port"105 check_fail $? "Ping worked after locking port, but before adding FDB entry"110 check_err $? "Ping did not work after locking port and adding FDB entry"131 check_err $? "Ping through vlan did not work before locking port"135 check_fail $? "Ping through vlan worked after locking port, but before adding FDB entry"140 check_err $? "Ping through vlan did not work after locking port and adding FDB entry"159 check_err $? "Ping6 did not work before locking port"164 check_fail $? "Ping6 worked after locking port, but before adding FDB entry"168 check_err $? "Ping6 did not work after locking port and adding FDB entry"185 check_err $? "Ping did not work before locking port"
22 the locking module below. Documentation and utilities for GFS2 can29 bool "GFS2 DLM locking"33 Multiple node locking module for GFS235 Most users of GFS2 will require this. It provides the locking
61 * LOCKING:81 * LOCKING:113 * LOCKING:136 * LOCKING:153 * LOCKING:202 * LOCKING:224 * LOCKING:252 * LOCKING:284 * LOCKING:312 * LOCKING:[all …]
5 * Defines OCFS2 Locking version values.14 * The protocol version for ocfs2 cluster locking. See dlmglue.c for17 * 1.0 - Initial locking version from ocfs2 1.4.
186 /* locking tokens */196 /* locking info table */217 /* Locking state for a locking range */327 * Locking Feature Descriptor. Contains flags indicating support for the328 * locking features described in the OPAL specification. The names match the341 * bit 1: locking enabled342 * bit 0: locking supported
4 Unreliable Guide To Locking12 Welcome, to Rusty's Remarkably Unreliable Guide to Kernel Locking13 issues. This document describes the locking systems in the Linux Kernel18 fundamentals of concurrency and locking for SMP.94 Locking in the Linux Kernel97 If I could give you one piece of advice on locking: **keep it simple**.134 You should always test your locking code with ``CONFIG_SMP`` and136 because it will still catch some kinds of locking bugs.141 Locking Only In User Context161 Locking Between User Context and Softirqs[all …]
66 * non-NULL. No locking is required.111 * No locking is required.129 * Locking is dependent on the driver.157 * Locking is dependent on the driver.174 * No locking is required.
22 * locking semantics of the file system using the protocol. It should25 * With version 11, we separate out the filesystem locking portion. The29 * filesystem locking changes.32 * - Negotiation of filesystem locking in the dlm join.60 * - introduction of "rw" lock and pushing meta/data locking down
7 Locking section in Linux Devlink Documentation11 locking. Drivers can use the existing ``devlink_*`` set of APIs, or12 new APIs prefixed by ``devl_*``. The older APIs handle all the locking
