Home
last modified time | relevance | path

Searched full:spinlocks (Results 1 – 25 of 142) sorted by relevance

123456

/linux/Documentation/locking/
H A Dspinlocks.rst22 worry about UP vs SMP issues: the spinlocks work correctly under both.
38 This is really the only really hard part about spinlocks: once you start
39 using spinlocks they tend to expand to areas you might not have noticed
40 before, because you have to make sure the spinlocks correctly protect the
41 shared data structures **everywhere** they are used. The spinlocks are most
52 Lesson 2: reader-writer spinlocks.
57 (rw_lock) versions of the spinlocks are sometimes useful. They allow multiple
62 simple spinlocks. Unless the reader critical section is long, you
63 are better off just using spinlocks.
91 NOTE! We are working hard to remove reader-writer spinlocks in most
[all …]
H A Dpi-futex.rst60 non-preemptible in a critical section, so the 'use spinlocks' argument
61 does not apply (user-space spinlocks have the same priority inversion
/linux/arch/mips/include/asm/octeon/
H A Dcvmx-spinlock.h29 * Implementation of spinlocks for Octeon CVMX. Although similar in
30 * function to Linux kernel spinlocks, they are not compatible.
31 * Octeon CVMX spinlocks are only used to synchronize with the boot
40 /* Spinlocks for Octeon */
46 * Spinlocks for Octeon CVMX
146 * Bit spinlocks
147 * These spinlocks use a single bit (bit 31) of a 32 bit word for locking.
/linux/Documentation/features/locking/queued-spinlocks/
H A Darch-support.txt2 # Feature name: queued-spinlocks
4 # description: arch supports queued spinlocks
/linux/lib/
H A Datomic64.c3 * Generic implementation of 64-bit atomics using spinlocks,
16 * We use a hashed array of spinlocks to provide exclusive access
19 * relatively small array of 16 spinlocks to avoid wasting too much
H A Dbust_spinlocks.c8 * bust_spinlocks() clears any spinlocks which would prevent oops, die(), BUG()
H A Ddebug_locks.c6 * spinlocks, rwlocks, mutexes and rwsems.
H A Dbucket_locks.c7 /* Allocate an array of spinlocks to be accessed by a hash. Two arguments
/linux/arch/sh/include/asm/
H A Dspinlock-cas.h23 * Your basic SMP spinlocks, allowing only a single CPU anywhere
44 * Read-write spinlocks, allowing multiple readers but only one writer.
H A Dspinlock-llsc.h15 * Your basic SMP spinlocks, allowing only a single CPU anywhere
82 * Read-write spinlocks, allowing multiple readers but only one writer.
H A Dspinlock.h16 #error "The configured cpu type does not support spinlocks"
/linux/arch/arc/include/asm/
H A Dspinlock.h75 * Read-write spinlocks, allowing multiple readers but only one writer.
228 * for ACQ and REL semantics respectively. However EX based spinlocks in arch_spin_lock()
290 * Read-write spinlocks, allowing multiple readers but only one writer.
/linux/arch/parisc/
H A DKconfig.debug11 which will detect unitialized spinlocks too.
/linux/Documentation/translations/zh_CN/locking/
H A Dindex.rst18 spinlocks
/linux/tools/memory-model/litmus-tests/
H A DMP+polockonce+poacquiresilsil.litmus6 * Do spinlocks provide order to outside observers using spin_is_locked()
H A DMP+polockmbonce+poacquiresilsil.litmus6 * Do spinlocks combined with smp_mb__after_spinlock() provide order
/linux/Documentation/kernel-hacking/
H A Dlocking.rst101 Two Main Types of Kernel Locks: Spinlocks and Mutexes
107 (spinning) until you can. Spinlocks are very small and fast, and can be
125 ``CONFIG_PREEMPT`` spinlocks do not exist at all. This is an excellent
130 is set, then spinlocks simply disable preemption, which is sufficient to
705 lock is required. In this case, it is simpler than using spinlocks,
706 although for anything non-trivial using spinlocks is clearer. The
879 (spinlocks, rwlocks and mutexes are not recursive in Linux). This is
890 with a single CPU (although not on UP compiles, since spinlocks vanish
1052 Both spinlocks and mutexes have read/write variants: ``rwlock_t`` and
1373 - ``Documentation/locking/spinlocks.rst``: Linus Torvalds' spinlocking
[all …]
/linux/rust/kernel/sync/
H A Dlock.rs6 //! spinlocks, raw spinlocks) to be provided with minimal effort.
112 /// or config defined (e.g., spinlocks). So we conservatively require them to be pinned in case
/linux/drivers/usb/usbip/
H A Dvudc_tx.c243 /* called with spinlocks held */
269 /* called with spinlocks held */
/linux/include/asm-generic/
H A Dmmiowb.h6 * Generic implementation of mmiowb() tracking for spinlocks.
/linux/kernel/configs/
H A Ddebug.config93 # Lock Debugging (spinlocks, mutexes, etc...)
/linux/fs/ocfs2/
H A Duptodate.h29 * should probably be spinlocks.
/linux/net/batman-adv/
H A Dhash.c75 * batadv_hash_set_lock_class() - Set specific lockdep class for hash spinlocks
/linux/drivers/hwspinlock/
H A Dhwspinlock_internal.h3 * Hardware spinlocks internal header
/linux/include/linux/mtd/
H A Dflashchip.h10 /* For spinlocks. sched.h includes spinlock.h from whichever directory it

123456