/linux/Documentation/RCU/ |
H A D | checklist.rst | 28 read-side primitives is critically important. 60 rcu_read_lock() and friends? These primitives are needed 92 primitives to add, remove, and replace elements on 109 appear atomic, as will individual atomic primitives. 112 of multiple atomic primitives. One alternative is to 157 various "_rcu()" list-traversal primitives, such 161 primitives. This is particularly useful in code that 168 list-traversal primitives can substitute for a good 172 and list_add_rcu() primitives must be used in order 184 The list_replace_rcu() and hlist_replace_rcu() primitives [all …]
|
H A D | lockdep.rst | 14 In addition, RCU provides the following primitives that check lockdep's 30 checking of rcu_dereference() primitives: 107 traversal primitives check for being called from within an RCU read-side 110 traversal primitives will complain only if the lockdep expression is
|
H A D | whatisRCU.rst | 186 This temporal primitives is used by a reader to inform the 273 the _rcu list-manipulation primitives such as list_add_rcu(). 340 primitives, such as list_for_each_entry_rcu() [2]_. 399 synchronize_rcu() and call_rcu() primitives used are the same for all three 400 flavors. However for protection (on the reader side), the primitives used vary 429 their assorted primitives. 512 rcu_assign_pointer() primitives from interfering with each other. 635 in terms of familiar locking primitives, and another that more closely 651 familiar locking primitives. Its overhead makes it a non-starter for 1173 update primitives. [all …]
|
/linux/drivers/gpu/drm/v3d/ |
H A D | v3d_perfmon.c | 13 …{"FEP", "FEP-valid-primitives-no-rendered-pixels", "[FEP] Valid primitives that result in no rende… 14 …{"FEP", "FEP-valid-primitives-rendered-pixels", "[FEP] Valid primitives for all rendered tiles (pr… 23 …{"PTB", "PTB-primitives-discarded-outside-viewport", "[PTB] Primitives discarded by being outside … 24 {"PTB", "PTB-primitives-need-clipping", "[PTB] Primitives that need clipping"}, 25 …{"PTB", "PTB-primitives-discarded-reversed", "[PTB] Primitives that are discarded because they are… 48 {"PTB", "PTB-primitives-binned", "[PTB] Total primitives binned"}, 108 …{"FEP", "FEP-valid-primitives-no-rendered-pixels", "[FEP] Valid primitives that result in no rende… 109 …{"FEP", "FEP-valid-primitives-rendered-pixels", "[FEP] Valid primitives for all rendered tiles (pr… 117 {"PTB", "PTB-primitives-need-clipping", "[PTB] Primitives that need clipping"}, 118 …{"PTB", "PTB-primitives-discarded-outside-viewport", "[PTB] Primitives discarded by being outside … [all …]
|
/linux/tools/memory-model/Documentation/ |
H A D | ordering.txt | 46 Note well that many of these primitives generate absolutely no code 50 ordering primitives provided for that purpose. For example, instead of 58 The Linux-kernel primitives that provide full ordering include: 65 o RCU's grace-period primitives. 79 memory-ordering primitives. It is surprisingly hard to remember their 113 Finally, RCU's grace-period primitives provide full ordering. These 114 primitives include synchronize_rcu(), synchronize_rcu_expedited(), 115 synchronize_srcu() and so on. However, these primitives have orders 117 Furthermore, RCU's grace-period primitives can only be invoked in 118 sleepable contexts. Therefore, RCU's grace-period primitives are [all …]
|
H A D | simple.txt | 52 Please use the standard locking primitives provided by the kernel rather 53 than rolling your own. For one thing, the standard primitives interact 54 properly with lockdep. For another thing, these primitives have been 131 Packaged primitives: Sequence locking 148 primitives. (LKMM does not yet know about sequence locking, so it is 153 Packaged primitives: RCU 168 Packaged primitives: Atomic operations 194 Reading code using these primitives is often also quite helpful. 222 Unordered primitives such as atomic_read(), atomic_set(), READ_ONCE(), and 223 WRITE_ONCE() can safely be used in some cases. These primitives provide [all …]
|
H A D | README | 17 like an overview of the types of low-level concurrency primitives 22 o You are familiar with the Linux-kernel concurrency primitives 80 primitives in terms of events. 92 primitives by category.
|
/linux/include/linux/ |
H A D | rculist.h | 39 * only if list_del() and similar primitives are not also used on the 101 * the _rcu list-traversal primitives, such as 122 * the _rcu list-traversal primitives, such as 147 * the _rcu list-traversal primitives, such as 179 * primitives, such as hlist_for_each_entry_rcu(). 307 * primitives such as list_add_rcu() as long as it's guarded by rcu_read_lock(). 351 * primitives such as list_add_rcu() as long as it's guarded by rcu_read_lock(). 370 * primitives such as list_add_rcu() as long as it's guarded by rcu_read_lock(). 389 * the _rcu list-mutation primitives such as list_add_rcu() 406 * the _rcu list-mutation primitives such as list_add_rcu() [all …]
|
H A D | processor.h | 2 /* Misc low level processor primitives */ 16 * of these primitives. It should not lock or take any other resource. 46 * primitives, above.
|
H A D | rculist_nulls.h | 31 * primitives, such as hlist_nulls_for_each_entry_rcu(). 71 * the _rcu list-traversal primitives, such as 94 * the _rcu list-traversal primitives, such as 125 * the _rcu list-traversal primitives, such as
|
H A D | rculist_bl.h | 43 * the _rcu list-traversal primitives, such as 66 * the _rcu list-traversal primitives, such as
|
/linux/Documentation/crypto/ |
H A D | api-kpp.rst | 1 Key-agreement Protocol Primitives (KPP) Cipher Algorithm Definitions 7 Key-agreement Protocol Primitives (KPP) Cipher API 11 :doc: Generic Key-agreement Protocol Primitives API 16 Key-agreement Protocol Primitives (KPP) Cipher Request Handle
|
/linux/include/acpi/ |
H A D | acpiosxf.h | 45 * OSL Initialization and shutdown primitives 82 * Spinlock primitives 101 * RAW spinlock primitives. If the OS does not provide them, fallback to 102 * spinlock primitives 122 * Semaphore primitives 144 * Mutex primitives. May be configured to use semaphores instead via
|
/linux/Documentation/devicetree/bindings/mailbox/ |
H A D | nvidia,tegra186-hsp.yaml | 7 title: NVIDIA Tegra Hardware Synchronization Primitives (HSP) 16 primitives for interprocessor communication. So the interprocessor 18 primitives, when operating between two processors not in an SMP
|
/linux/drivers/scsi/isci/ |
H A D | phy.h | 277 * primitives received. 283 * primitives transmitted. 295 * primitives received. 301 * primitives transmitted. 307 * primitives received.
|
/linux/include/linux/mtd/ |
H A D | xip.h | 3 * MTD primitives for XIP support 68 #warning "missing IRQ and timer primitives for XIP MTD support"
|
/linux/Documentation/core-api/ |
H A D | genericirq.rst | 121 primitives referenced by the assigned chip descriptor structure. 183 The helper functions call the chip primitives and are used by the 279 The simple flow handler does not call any handler/chip primitives. 367 These primitives are strictly intended to mean what they say: ack means 386 chip primitives. The per-irq structure is protected via desc->lock, by
|
/linux/Documentation/locking/ |
H A D | locktypes.rst | 12 The kernel provides a variety of locking primitives which can be divided 34 versions of these primitives. In short, don't acquire sleeping locks from 59 preemption and interrupt disabling primitives. Contrary to other locking 165 interrupt disabling and enabling primitives: 177 primitives: 180 of the protection scope while the regular primitives are scopeless and
|
/linux/drivers/firmware/arm_scmi/transports/ |
H A D | Kconfig | 63 primitives all over instead. If unsure say N. 121 primitives all over instead. If unsure say N.
|
/linux/arch/riscv/include/asm/ |
H A D | mmio.h | 84 * Unordered I/O memory access primitives. These are even more relaxed than 102 * Relaxed I/O memory access primitives. These follow the Device memory 129 * I/O memory access primitives. Reads are ordered relative to any following
|
/linux/crypto/ |
H A D | kpp.c | 3 * Key-agreement Protocol Primitives (KPP) 143 MODULE_DESCRIPTION("Key-agreement Protocol Primitives");
|
/linux/kernel/rcu/ |
H A D | rcutorture.c | 87 torture_param(bool, gp_cond, false, "Use conditional/async GP wait primitives"); 88 torture_param(bool, gp_cond_exp, false, "Use conditional/async expedited GP wait primitives"); 89 torture_param(bool, gp_cond_full, false, "Use conditional/async full-state GP wait primitives"); 91 "Use conditional/async full-stateexpedited GP wait primitives"); 92 torture_param(bool, gp_exp, false, "Use expedited GP wait primitives"); 93 torture_param(bool, gp_normal, false, "Use normal (non-expedited) GP wait primitives"); 94 torture_param(bool, gp_poll, false, "Use polling GP wait primitives"); 95 torture_param(bool, gp_poll_exp, false, "Use polling expedited GP wait primitives"); 96 torture_param(bool, gp_poll_full, false, "Use polling full-state GP wait primitives"); 97 torture_param(bool, gp_poll_exp_full, false, "Use polling full-state expedited GP wait primitives"); [all …]
|
/linux/include/crypto/ |
H A D | kpp.h | 3 * Key-agreement Protocol Primitives (KPP) 55 * struct kpp_alg - generic key-agreement protocol primitives 92 * DOC: Generic Key-agreement Protocol Primitives API
|
/linux/Documentation/process/ |
H A D | volatile-considered-harmful.rst | 21 Like volatile, the kernel primitives which make concurrent access to data 38 primitives act as memory barriers - they are explicitly written to do so -
|
/linux/Documentation/driver-api/usb/ |
H A D | dma.rst | 44 For those specific cases, USB has primitives to allocate less expensive 55 Most drivers should **NOT** be using these primitives; they don't need
|