| /linux/tools/include/linux/ |
| A 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/include/linux/ |
| A 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/Documentation/core-api/ |
| A 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/tools/memory-model/Documentation/ |
| A 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
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
1375 propagate to every CPU and to RAM before F executes.
1450 propagates to C's CPU before the end of C must propagate to
1454 propagates to G's CPU before the start of G must propagate
2061 the barrier to propagate to other CPUs before stores that are
[all …]
|
| /linux/Documentation/filesystems/ |
| A 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
|
| A D | zonefs.rst | 212 errors can propagate through a stream of cached sequential data for a zone
|
| /linux/Documentation/trace/coresight/ |
| A 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
|
| A 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/Documentation/filesystems/nfs/ |
| A D | reexport.rst | 20 The "crossmnt" export does not propagate "fsid=", so it will not allow
|
| /linux/tools/lib/ |
| A D | rbtree.c | 428 .propagate = dummy_propagate,
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| A D | devices.rst | 81 it'll propagate down and after revalidating B's entries, the whitelist entry
|
| /linux/lib/ |
| A D | rbtree.c | 429 .propagate = dummy_propagate,
|
| /linux/Documentation/admin-guide/ |
| A 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
|
| A D | sysfs-rules.rst | 177 propagate errors wherever possible. Common errors include, but are not
|
| /linux/arch/m68k/fpsp040/ |
| A D | round.S | 214 addql #1,LOCAL_HI(%a0) |propagate carry
233 addql #1,LOCAL_HI(%a0) |propagate carry
|
| /linux/scripts/ |
| A D | spelling.txt | 1177 propigate||propagate
1180 propogate||propagate
|
| /linux/Documentation/userspace-api/ |
| A D | landlock.rst | 240 propagate the hierarchy constraints. To protect against privilege escalations
|
| /linux/Documentation/locking/ |
| A D | ww-mutex-design.rst | 136 Furthermore the lock helper can use propagate the -EALREADY return code back to
|
| A D | rt-mutex-design.rst | 465 the lock's waiter tree and propagate the pi chain of the lock as well
|
| /linux/Documentation/input/ |
| A D | multi-touch-protocol.rst | 65 identified contact, and use that slot to propagate changes for the contact.
|
| /linux/Documentation/userspace-api/media/v4l/ |
| A D | dev-subdev.rst | 183 Drivers automatically propagate formats inside sub-devices. When a try
|
| /linux/kernel/sched/ |
| A D | sched.h | 583 long propagate; member
|
| A D | fair.c | 3570 cfs_rq->propagate = 1; in add_tg_cfs_propagate()
3583 if (!gcfs_rq->propagate) in propagate_entity_load_avg()
3586 gcfs_rq->propagate = 0; in propagate_entity_load_avg()
3621 if (gcfs_rq->propagate) in skip_blocked_update()
|
| /linux/Documentation/networking/ |
| A D | switchdev.rst | 356 FIB_EVENT_RULE_DEL used to propagate FIB rule changes
|
| /linux/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| A D | Expedited-Grace-Periods.rst | 358 Tasks E and F will propagate up the ``rcu_node`` combining tree, with
|