Searched refs:propagate (Results 1 – 15 of 15) sorted by relevance
| /linux-4.4.14/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-4.4.14/include/linux/ |
| D | rbtree_augmented.h | 39 void (*propagate)(struct rb_node *node, struct rb_node *stop); member
213 augment->propagate(parent, successor); in __rb_erase_augmented()
236 augment->propagate(tmp, NULL); in __rb_erase_augmented()
|
| /linux-4.4.14/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-4.4.14/block/ |
| D | cfq-iosched.c | 1305 bool propagate; in cfq_group_service_tree_add() local
1327 propagate = !pos->nr_active++; in cfq_group_service_tree_add()
1338 if (propagate) { in cfq_group_service_tree_add()
1340 propagate = !parent->nr_active++; in cfq_group_service_tree_add()
1379 bool propagate; in cfq_group_service_tree_del() local
1385 propagate = !--pos->nr_active; in cfq_group_service_tree_del()
1388 while (propagate) { in cfq_group_service_tree_del()
1398 propagate = !--parent->nr_active; in cfq_group_service_tree_del()
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | devices.txt | 72 it'll propagate down and after revalidating B's entries, the whitelist entry
|
| D | memory.txt | 807 memory or thrashing. So, organize the cgroups wisely, or propagate the
|
| /linux-4.4.14/scripts/ |
| D | spelling.txt | 775 propigate||propagate
777 propogate||propagate
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | round.S | 214 addql #1,LOCAL_HI(%a0) |propagate carry
233 addql #1,LOCAL_HI(%a0) |propagate carry
|
| /linux-4.4.14/Documentation/ |
| D | sysfs-rules.txt | 170 propagate errors wherever possible. Common errors include, but are not
|
| D | memory-barriers.txt | 501 mechanisms should propagate the indirect effects of a memory barrier
2629 cacheline over to the accessing CPU and propagate the effects upon conflict.
|
| /linux-4.4.14/Documentation/locking/ |
| D | ww-mutex-design.txt | 110 Furthermore the lock helper can use propagate the -EALREADY return code back to
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | networking.xml.db | 49 API-skb-propagate-pfmemalloc
|
| /linux-4.4.14/Documentation/input/ |
| D | multi-touch-protocol.txt | 58 identified contact, and use that slot to propagate changes for the contact.
|
| /linux-4.4.14/Documentation/trace/ |
| D | events.txt | 256 fields can be guaranteed to propagate successfully to all events.
|
| /linux-4.4.14/Documentation/networking/ |
| D | bonding.txt | 2219 Its purpose is to propagate link failures from logically "exterior" ports
|