| /Linux-v4.19/include/linux/ |
| D | rbtree_augmented.h | 40 void (*propagate)(struct rb_node *node, struct rb_node *stop); member
105 .propagate = rbname ## _propagate, \
244 augment->propagate(parent, successor); in __rb_erase_augmented()
267 augment->propagate(tmp, NULL); in __rb_erase_augmented()
|
| /Linux-v4.19/tools/include/linux/ |
| D | rbtree_augmented.h | 42 void (*propagate)(struct rb_node *node, struct rb_node *stop); member
211 augment->propagate(parent, successor); in __rb_erase_augmented()
232 augment->propagate(tmp, NULL); in __rb_erase_augmented()
|
| /Linux-v4.19/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
|
| D | xfs.txt | 357 Defines how fast XFS should propagate an error upwards when a specific
358 error is found during the filesystem operation. It can propagate
438 the filesystem will propagate the error. The retry count for a given
|
| /Linux-v4.19/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
|
| /Linux-v4.19/tools/memory-model/Documentation/ |
| D | explanation.txt | 808 on C to propagate to C' before any po-later stores do.
812 stores executed on C) is forced to propagate to C' before the
817 propagate to all other CPUs before any instructions po-after
821 affects stores from other CPUs that propagate to CPU C before the
851 and W ->cumul-fence W', then W must propagate to any given CPU
853 require W to propagate to C before W' propagates to C'.
877 Propagation: This requires that certain stores propagate to
1125 smp_wmb() forces P0's store to x to propagate to P1 before the store
1175 wait for all of its po-earlier stores to propagate to every other CPU
1211 for the memory subsystem not to propagate W to R's CPU until after R
[all …]
|
| /Linux-v4.19/Documentation/cgroup-v1/ |
| D | devices.txt | 72 it'll propagate down and after revalidating B's entries, the whitelist entry
|
| D | memory.txt | 807 - "hierarchy": events always propagate up to the root, similar to the default
|
| /Linux-v4.19/block/ |
| D | cfq-iosched.c | 1298 bool propagate; in cfq_group_service_tree_add() local
1320 propagate = !pos->nr_active++; in cfq_group_service_tree_add()
1331 if (propagate) { in cfq_group_service_tree_add()
1333 propagate = !parent->nr_active++; in cfq_group_service_tree_add()
1381 bool propagate; in cfq_group_service_tree_del() local
1387 propagate = !--pos->nr_active; in cfq_group_service_tree_del()
1390 while (propagate) { in cfq_group_service_tree_del()
1400 propagate = !--parent->nr_active; in cfq_group_service_tree_del()
|
| /Linux-v4.19/lib/ |
| D | rbtree.c | 445 .propagate = dummy_propagate,
|
| /Linux-v4.19/arch/m68k/fpsp040/ |
| D | round.S | 214 addql #1,LOCAL_HI(%a0) |propagate carry
233 addql #1,LOCAL_HI(%a0) |propagate carry
|
| /Linux-v4.19/scripts/ |
| D | spelling.txt | 966 propigate||propagate
968 propogate||propagate
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | sysfs-rules.rst | 177 propagate errors wherever possible. Common errors include, but are not
|
| /Linux-v4.19/Documentation/locking/ |
| D | ww-mutex-design.txt | 134 Furthermore the lock helper can use propagate the -EALREADY return code back to
|
| D | rt-mutex-design.txt | 453 the lock's waiter tree and propagate the pi chain of the lock as well
|
| /Linux-v4.19/Documentation/networking/ |
| D | switchdev.txt | 322 FIB_EVENT_RULE_ADD, FIB_EVENT_RULE_DEL: used to propagate FIB rule changes
|
| D | bonding.txt | 2219 Its purpose is to propagate link failures from logically "exterior" ports
|
| /Linux-v4.19/Documentation/input/ |
| D | multi-touch-protocol.rst | 65 identified contact, and use that slot to propagate changes for the contact.
|
| /Linux-v4.19/kernel/sched/ |
| D | sched.h | 525 long propagate; member
|
| D | fair.c | 3306 cfs_rq->propagate = 1; in add_tg_cfs_propagate()
3319 if (!gcfs_rq->propagate) in propagate_entity_load_avg()
3322 gcfs_rq->propagate = 0; in propagate_entity_load_avg()
3353 if (gcfs_rq->propagate) in skip_blocked_update()
|
| /Linux-v4.19/Documentation/vm/ |
| D | hmm.rst | 160 to propagate CPU page tables::
|
| /Linux-v4.19/Documentation/livepatch/ |
| D | callbacks.txt | 396 code will propagate back to the module-loading subsystem. The result is
|
| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| D | dev-subdev.rst | 178 Drivers automatically propagate formats inside sub-devices. When a try
|
| /Linux-v4.19/Documentation/trace/ |
| D | events.rst | 254 fields can be guaranteed to propagate successfully to all events.
|
| /Linux-v4.19/Documentation/ |
| D | memory-barriers.txt | 547 mechanisms should propagate the indirect effects of a memory barrier
2740 cacheline over to the accessing CPU and propagate the effects upon conflict.
|
