/linux-6.8/include/linux/atomic/ |
D | atomic-instrumented.h | 95 * Atomically updates @v to (@v + @i) with relaxed ordering. 113 * Atomically updates @v to (@v + @i) with full ordering. 132 * Atomically updates @v to (@v + @i) with acquire ordering. 150 * Atomically updates @v to (@v + @i) with release ordering. 169 * Atomically updates @v to (@v + @i) with relaxed ordering. 187 * Atomically updates @v to (@v + @i) with full ordering. 206 * Atomically updates @v to (@v + @i) with acquire ordering. 224 * Atomically updates @v to (@v + @i) with release ordering. 243 * Atomically updates @v to (@v + @i) with relaxed ordering. 261 * Atomically updates @v to (@v - @i) with relaxed ordering. [all …]
|
D | atomic-long.h | 111 * Atomically updates @v to (@v + @i) with relaxed ordering. 132 * Atomically updates @v to (@v + @i) with full ordering. 153 * Atomically updates @v to (@v + @i) with acquire ordering. 174 * Atomically updates @v to (@v + @i) with release ordering. 195 * Atomically updates @v to (@v + @i) with relaxed ordering. 216 * Atomically updates @v to (@v + @i) with full ordering. 237 * Atomically updates @v to (@v + @i) with acquire ordering. 258 * Atomically updates @v to (@v + @i) with release ordering. 279 * Atomically updates @v to (@v + @i) with relaxed ordering. 300 * Atomically updates @v to (@v - @i) with relaxed ordering. [all …]
|
D | atomic-arch-fallback.h | 537 * Atomically updates @v to (@v + @i) with relaxed ordering. 554 * Atomically updates @v to (@v + @i) with full ordering. 581 * Atomically updates @v to (@v + @i) with acquire ordering. 608 * Atomically updates @v to (@v + @i) with release ordering. 634 * Atomically updates @v to (@v + @i) with relaxed ordering. 657 * Atomically updates @v to (@v + @i) with full ordering. 684 * Atomically updates @v to (@v + @i) with acquire ordering. 711 * Atomically updates @v to (@v + @i) with release ordering. 737 * Atomically updates @v to (@v + @i) with relaxed ordering. 760 * Atomically updates @v to (@v - @i) with relaxed ordering. [all …]
|
/linux-6.8/Documentation/RCU/ |
D | checklist.rst | 32 for lockless updates. This does result in the mildly 34 rcu_read_unlock() are used to protect updates, however, this 45 c. restricting updates to a single task. 87 be running while updates are in progress. There are a number 106 c. Make updates appear atomic to readers. For example, 107 pointer updates to properly aligned fields will 118 d. Carefully order the updates and the reads so that readers 190 e. Updates must ensure that initialization of a given 222 Restructure your code so that it batches the updates, allowing 287 primitive will correspondingly delay updates. In contrast, [all …]
|
/linux-6.8/fs/xfs/ |
D | xfs_rmap_item.h | 17 * that records the associated rmapbt updates. Typically, the first 19 * transactions containing rmapbt updates, and finally transactions with any 20 * bnobt/cntbt updates. 25 * (rmapbt/bnobt/cntbt) metadata updates in the non-first transaction. 63 * some rmapbt updates mentioned in an earlier rui item have been performed.
|
D | xfs_bmap_item.h | 17 * that records the associated bmbt updates. 22 * bmbt metadata updates in the non-first transaction. 60 * some bmbt updates mentioned in an earlier bui item have been performed.
|
D | xfs_refcount_item.h | 17 * transaction that records the associated refcountbt updates. 22 * to replay the refcountbt metadata updates. 62 * fact that some refcountbt updates mentioned in an earlier cui item
|
/linux-6.8/fs/bcachefs/ |
D | journal.h | 8 * The primary purpose of the journal is to log updates (insertions) to the 9 * b-tree, to avoid having to do synchronous updates to the b-tree on disk. 13 * but did handle unclean shutdowns by doing all index updates synchronously 16 * Updates to interior nodes still happen synchronously and without the journal 17 * (for simplicity) - this may change eventually but updates to interior nodes 26 * For synchronous updates (where we're waiting on the index update to hit 30 * Synchronous updates are specified by passing a closure (@flush_cl) to 73 * Open/dirty journal entries are journal entries that contain b-tree updates 92 * Journalling of index updates is done at the same time as the b-tree itself is
|
D | journal_seq_blacklist.c | 12 * To guarantee order of btree updates after a crash, we need to detect when a 14 * successfully written, and ignore it - effectively ignoring any btree updates 18 * updates that weren't written to the journal yet: if b was updated after a, 19 * but b was flushed and not a - oops; on recovery we'll find that the updates 20 * to b happened, but not the updates to a that happened before it. 28 * contain updates for; then, on startup, the btree code queries the journal
|
/linux-6.8/drivers/net/ethernet/intel/fm10k/ |
D | fm10k_common.c | 299 * fm10k_update_hw_base_48b - Updates 48-bit statistic base value 320 * fm10k_update_hw_stats_tx_q - Updates TX queue statistics counters 325 * Function updates the TX queue statistics counters that are related to the 371 * fm10k_update_hw_stats_rx_q - Updates RX queue statistics counters 376 * Function updates the RX queue statistics counters that are related to the 427 * fm10k_update_hw_stats_q - Updates queue statistics counters 433 * Function updates the queue statistics counters that are related to the 453 * Function invalidates the index values for the queues so any updates that
|
/linux-6.8/drivers/base/firmware_loader/ |
D | Kconfig | 15 o /lib/firmware/updates/UTS_RELEASE 16 o /lib/firmware/updates 220 bool "Enable users to initiate firmware updates using sysfs" 225 sysfs interface that allows firmware updates to be initiated from 229 to support cards that rely on user-initiated updates for firmware files.
|
/linux-6.8/drivers/gpu/drm/msm/ |
D | msm_atomic.c | 82 * Flush hardware updates: in msm_atomic_async_commit() 232 * Push atomic updates down to hardware: in msm_atomic_commit_tail() 242 /* async updates are limited to single-crtc updates: */ in msm_atomic_commit_tail() 288 * Flush hardware updates: in msm_atomic_commit_tail()
|
/linux-6.8/Documentation/ABI/testing/ |
D | sysfs-bus-coresight-devices-trbe | 12 Description: (Read) Shows if TRBE updates in the memory are with access 13 and dirty flag updates as well. This value is fetched from
|
D | sysfs-bus-counter | 208 Rising edges on signal A updates the respective count. 213 signal A updates the respective count; if the direction 215 updates the respective count. Quadrature encoding 220 signal B updates the respective count; if the direction 222 updates the respective count. Quadrature encoding 226 Any state transition on quadrature pair signal A updates 231 Any state transition on quadrature pair signal B updates 237 updates the respective count. Quadrature encoding
|
/linux-6.8/scripts/atomic/kerneldoc/ |
D | try_cmpxchg | 8 * If (@v == @old), atomically updates @v to @new with ${desc_order} ordering. 9 * Otherwise, updates @old to the current value of @v.
|
/linux-6.8/drivers/net/ |
D | LICENSE.SRC | 14 on an "as-is" basis. No further updates to this software should be 15 expected. Although updates may occur, no commitment exists.
|
/linux-6.8/Documentation/core-api/ |
D | entry.rst | 4 All transitions between execution domains require state updates which are 5 subject to strict ordering constraints. State updates are required for the 167 irq_enter_rcu() updates the preemption count which makes in_hardirq() 212 The state update on entry is handled in irqentry_nmi_enter() which updates 278 while handling an NMI. So NMI entry code has to be reentrant and state updates
|
/linux-6.8/drivers/gpu/drm/xe/ |
D | xe_migrate.c | 138 /* And one slot reserved for the 4KiB page table updates */ in xe_migrate_prepare_vm() 273 * for async VM updates. in xe_migrate_prepare_vm() 276 * everywhere, this allows lockless updates to scratch pages by using in xe_migrate_prepare_vm() 1159 const struct xe_vm_pgtable_update *updates, in xe_migrate_update_pgtables_cpu() argument 1189 const struct xe_vm_pgtable_update *update = &updates[i]; in xe_migrate_update_pgtables_cpu() 1237 * @updates: An array of update descriptors. 1238 * @num_updates: Number of descriptors in @updates. 1248 * using the default engine for the updates, they will be performed in the 1250 * synchronization is needed for overlapping updates to maintain page-table 1251 * consistency. Note that the meaing of "overlapping" is that the updates [all …]
|
/linux-6.8/drivers/gpu/drm/amd/amdgpu/ |
D | amdgpu_hmm.c | 35 * about updates on the page tables of a process. 122 * amdgpu_hmm_register - register a BO for notifier updates 142 * amdgpu_hmm_unregister - unregister a BO for notifier updates 146 * Remove any registration of mmu notifier updates from the buffer object.
|
/linux-6.8/Documentation/driver-api/firmware/ |
D | fw_search_path.rst | 9 * /lib/firmware/updates/UTS_RELEASE/ 10 * /lib/firmware/updates/
|
/linux-6.8/drivers/gpu/drm/radeon/ |
D | radeon_mn.c | 88 * radeon_mn_register - register a BO for notifier updates 116 * radeon_mn_unregister - unregister a BO for notifier updates 120 * Remove any registration of MMU notifier updates from the buffer object.
|
/linux-6.8/drivers/net/ethernet/netronome/nfp/flower/ |
D | main.h | 268 * @stats: Stored stats updates for flower rules 269 * @stats_lock: Lock for flower rule stats updates 289 * @qos_stats_lock: Lock on qos stats updates 290 * @meter_stats_lock: Lock on meter stats updates 299 * @predt_lock: Lock to serialise predt/neigh table updates 342 spinlock_t predt_lock; /* Lock to serialise predt/neigh table updates */ 349 * @curr_stats: Currently stored stats updates for qos info 350 * @prev_stats: Previously stored updates for qos info
|
/linux-6.8/include/linux/mfd/ |
D | lochnagar.h | 29 * @analogue_config_lock: Lock used to protect updates in the analogue 38 /* Lock to protect updates to the analogue configuration */
|
/linux-6.8/include/vdso/ |
D | helpers.h | 34 * updates to vd[x].seq and it is possible that the value seen by the in vdso_write_begin() 47 * updates to vd[x].seq and it is possible that the value seen by the in vdso_write_end()
|
/linux-6.8/arch/powerpc/kernel/ |
D | pci-hotplug.c | 8 * Updates, 2005, John Rose <johnrose@austin.ibm.com> 9 * Updates, 2005, Linas Vepstas <linas@austin.ibm.com> 10 * Updates, 2013, Gavin Shan <shangw@linux.vnet.ibm.com>
|