| /linux-5.19.10/tools/include/linux/ |
| D | rbtree_augmented.h | 30 void (*propagate)(struct rb_node *node, struct rb_node *stop); member
104 .propagate = RBNAME ## _propagate, \
263 augment->propagate(parent, successor); in __rb_erase_augmented()
286 augment->propagate(tmp, NULL); in __rb_erase_augmented()
|
| /linux-5.19.10/include/linux/ |
| D | rbtree_augmented.h | 28 void (*propagate)(struct rb_node *node, struct rb_node *stop); member
102 .propagate = RBNAME ## _propagate, \
274 augment->propagate(parent, successor); in __rb_erase_augmented()
295 augment->propagate(tmp, NULL); in __rb_erase_augmented()
|
| /linux-5.19.10/Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 45 and all propagated stores from other CPUs must propagate to all
53 must propagate to all other CPUs before the release operation
60 po-later stores on the same CPU must propagate to all other CPUs
|
| /linux-5.19.10/tools/memory-model/litmus-tests/ |
| D | MP+unlocklockonceonce+fencermbonceonce.litmus | 7 * first must propagate to each CPU before stores in the second do, even if
|
| /linux-5.19.10/Documentation/filesystems/ |
| D | sharedsubtree.rst | 87 only propagate towards it.
260 A 'peer group' is defined as a group of vfsmounts that propagate
285 mount/unmount events are received. Events do not propagate from
428 mount/unmount on 'A' do not propagate anywhere else. Similarly
429 mount/unmount on 'C' do not propagate anywhere else.
573 Example: Let's say 'B1', 'B2', 'B3' are shared mounts that propagate to
603 If 'A' is shared, then 'B' is also shared and 'A' and 'B' propagate to
670 will the mount propagate to 'B' and 'C' ?
905 In the above figure A,B,C and D all are shared and propagate to each
908 'E' is also shared with 'K' and they propagate to each other. And
|
| /linux-5.19.10/tools/memory-model/Documentation/ |
| D | explanation.txt | 855 on C to propagate to C' before any po-later stores do.
859 stores executed on C) is forced to propagate to C' before the
864 propagate to all other CPUs before any instructions po-after
868 affects stores from other CPUs that propagate to CPU C before the
898 and W ->cumul-fence W', then W must propagate to any given CPU
900 require W to propagate to C before W' propagates to C'.
924 Propagation: This requires that certain stores propagate to
1154 smp_wmb() forces P0's store to x to propagate to P1 before the store
1202 po-earlier stores to propagate to every other CPU in the system; then
1238 for the memory subsystem not to propagate W to R's CPU until after R
[all …]
|
| /linux-5.19.10/Documentation/networking/ |
| D | mptcp-sysctl.rst | 58 traffic to propagate all of the related events and commands.
|
| D | switchdev.rst | 356 FIB_EVENT_RULE_DEL used to propagate FIB rule changes
|
| /linux-5.19.10/Documentation/admin-guide/hw-vuln/ |
| D | processor_mmio_stale_data.rst | 11 not transient execution attacks. However, these vulnerabilities may propagate
29 Stale data may propagate from fill buffers (FB) into the non-coherent portion
182 Control register writes by CPU during C-state transition can propagate data
|
| /linux-5.19.10/Documentation/trace/coresight/ |
| D | coresight-ect.rst | 16 devices via numbered channels, in order to propagate events between devices.
170 * ``chan_gate_enable``: Write operation sets the CTI gate to propagate
|
| D | coresight.rst | 281 as a sink, or as a link to propagate further along the chain::
617 individual CTIs and components, and can propagate these between all CTIs via
|
| /linux-5.19.10/Documentation/filesystems/nfs/ |
| D | reexport.rst | 20 The "crossmnt" export does not propagate "fsid=", so it will not allow
|
| /linux-5.19.10/tools/lib/ |
| D | rbtree.c | 428 .propagate = dummy_propagate,
|
| /linux-5.19.10/Documentation/admin-guide/cgroup-v1/ |
| D | devices.rst | 81 it'll propagate down and after revalidating B's entries, the whitelist entry
|
| /linux-5.19.10/lib/ |
| D | rbtree.c | 429 .propagate = dummy_propagate,
|
| /linux-5.19.10/Documentation/admin-guide/ |
| D | xfs.rst | 389 Defines how fast XFS should propagate an error upwards when a specific
390 error is found during the filesystem operation. It can propagate
470 the filesystem will propagate the error. The retry count for a given
|
| D | sysfs-rules.rst | 177 propagate errors wherever possible. Common errors include, but are not
|
| /linux-5.19.10/arch/m68k/fpsp040/ |
| D | round.S | 214 addql #1,LOCAL_HI(%a0) |propagate carry
233 addql #1,LOCAL_HI(%a0) |propagate carry
|
| /linux-5.19.10/scripts/ |
| D | spelling.txt | 1189 propigate||propagate
1192 propogate||propagate
|
| /linux-5.19.10/Documentation/locking/ |
| D | ww-mutex-design.rst | 136 Furthermore the lock helper can use propagate the -EALREADY return code back to
|
| D | rt-mutex-design.rst | 465 the lock's waiter tree and propagate the pi chain of the lock as well
|
| /linux-5.19.10/Documentation/input/ |
| D | multi-touch-protocol.rst | 65 identified contact, and use that slot to propagate changes for the contact.
|
| /linux-5.19.10/Documentation/userspace-api/media/v4l/ |
| D | dev-subdev.rst | 183 Drivers automatically propagate formats inside sub-devices. When a try
|
| /linux-5.19.10/kernel/sched/ |
| D | sched.h | 575 long propagate; member
|
| D | fair.c | 3651 cfs_rq->propagate = 1; in add_tg_cfs_propagate()
3664 if (!gcfs_rq->propagate) in propagate_entity_load_avg()
3667 gcfs_rq->propagate = 0; in propagate_entity_load_avg()
3702 if (gcfs_rq->propagate) in skip_blocked_update()
|