Searched refs:propagate (Results 1 – 24 of 24) sorted by relevance
| /Linux-v5.4/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-v5.4/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()
297 augment->propagate(tmp, NULL); in __rb_erase_augmented()
|
| /Linux-v5.4/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-v5.4/Documentation/filesystems/ |
| D | sharedsubtree.txt | 77 only propagate towards it.
247 A 'peer group' is defined as a group of vfsmounts that propagate
271 mount/unmount events are received. Events do not propagate from
409 mount/unmount on 'A' do not propagate anywhere else. Similarly
410 mount/unmount on 'C' do not propagate anywhere else.
550 Example: Let's say 'B1', 'B2', 'B3' are shared mounts that propagate to
580 If 'A' is shared, then 'B' is also shared and 'A' and 'B' propagate to
641 will the mount propagate to 'B' and 'C' ?
856 In the above figure A,B,C and D all are shared and propagate to each
859 'E' is also shared with 'K' and they propagate to each other. And
|
| /Linux-v5.4/tools/memory-model/Documentation/ |
| D | explanation.txt | 804 on C to propagate to C' before any po-later stores do.
808 stores executed on C) is forced to propagate to C' before the
813 propagate to all other CPUs before any instructions po-after
817 affects stores from other CPUs that propagate to CPU C before the
847 and W ->cumul-fence W', then W must propagate to any given CPU
849 require W to propagate to C before W' propagates to C'.
873 Propagation: This requires that certain stores propagate to
1099 smp_wmb() forces P0's store to x to propagate to P1 before the store
1149 wait for all of its po-earlier stores to propagate to every other CPU
1185 for the memory subsystem not to propagate W to R's CPU until after R
[all …]
|
| /Linux-v5.4/Documentation/admin-guide/cgroup-v1/ |
| D | devices.rst | 81 it'll propagate down and after revalidating B's entries, the whitelist entry
|
| D | memory.rst | 918 - "hierarchy": events always propagate up to the root, similar to the default
|
| /Linux-v5.4/tools/lib/ |
| D | rbtree.c | 428 .propagate = dummy_propagate,
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | xfs.rst | 355 Defines how fast XFS should propagate an error upwards when a specific
356 error is found during the filesystem operation. It can propagate
436 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-v5.4/lib/ |
| D | rbtree.c | 429 .propagate = dummy_propagate,
|
| /Linux-v5.4/arch/m68k/fpsp040/ |
| D | round.S | 214 addql #1,LOCAL_HI(%a0) |propagate carry
233 addql #1,LOCAL_HI(%a0) |propagate carry
|
| /Linux-v5.4/scripts/ |
| D | spelling.txt | 1048 propigate||propagate
1050 propogate||propagate
|
| /Linux-v5.4/Documentation/networking/ |
| D | switchdev.txt | 320 FIB_EVENT_RULE_ADD, FIB_EVENT_RULE_DEL: used to propagate FIB rule changes
|
| D | bonding.txt | 2229 Its purpose is to propagate link failures from logically "exterior" ports
|
| /Linux-v5.4/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-v5.4/Documentation/input/ |
| D | multi-touch-protocol.rst | 65 identified contact, and use that slot to propagate changes for the contact.
|
| /Linux-v5.4/kernel/sched/ |
| D | sched.h | 536 long propagate; member
|
| D | fair.c | 3379 cfs_rq->propagate = 1; in add_tg_cfs_propagate()
3392 if (!gcfs_rq->propagate) in propagate_entity_load_avg()
3395 gcfs_rq->propagate = 0; in propagate_entity_load_avg()
3429 if (gcfs_rq->propagate) in skip_blocked_update()
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | dev-subdev.rst | 185 Drivers automatically propagate formats inside sub-devices. When a try
|
| /Linux-v5.4/Documentation/trace/ |
| D | events.rst | 254 fields can be guaranteed to propagate successfully to all events.
|
| /Linux-v5.4/Documentation/vm/ |
| D | hmm.rst | 156 to propagate CPU page tables::
|
| /Linux-v5.4/Documentation/ |
| D | memory-barriers.txt | 546 mechanisms should propagate the indirect effects of a memory barrier
2690 cacheline over to the accessing CPU and propagate the effects upon conflict.
|
