| /linux-6.15/include/linux/ |
| H A D | rbtree_augmented.h | 28 void (*propagate)(struct rb_node *node, struct rb_node *stop); member 83 augment->propagate(parent, NULL); /* suboptimal */ in rb_add_augmented_cached() 128 .propagate = RBNAME ## _propagate, \ 300 augment->propagate(parent, successor); in __rb_erase_augmented() 321 augment->propagate(tmp, NULL); in __rb_erase_augmented()
|
| /linux-6.15/tools/include/linux/ |
| H 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-6.15/tools/memory-model/litmus-tests/ |
| H A D | MP+unlocklockonceonce+fencermbonceonce.litmus | 7 * first must propagate to each CPU before stores in the second do, even if
|
| /linux-6.15/Documentation/core-api/ |
| H 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-6.15/tools/sched_ext/ |
| H A D | scx_flatcg.bpf.c | 457 bool propagate = false; in update_active_weight_sums() local 480 propagate = true; in update_active_weight_sums() 488 propagate = true; in update_active_weight_sums() 496 if (!propagate) in update_active_weight_sums()
|
| /linux-6.15/Documentation/netlink/specs/ |
| H A D | rt_route.yaml | 167 name: ttl-propagate 305 - ttl-propagate
|
| /linux-6.15/Documentation/filesystems/ |
| H A D | sharedsubtree.rst | 87 only propagate towards it. 261 A 'peer group' is defined as a group of vfsmounts that propagate 286 mount/unmount events are received. Events do not propagate from 429 mount/unmount on 'A' do not propagate anywhere else. Similarly 430 mount/unmount on 'C' do not propagate anywhere else. 574 Example: Let's say 'B1', 'B2', 'B3' are shared mounts that propagate to 604 If 'A' is shared, then 'B' is also shared and 'A' and 'B' propagate to 672 will the mount propagate to 'B' and 'C' ? 909 In the above figure A,B,C and D all are shared and propagate to each 912 'E' is also shared with 'K' and they propagate to each other. And
|
| /linux-6.15/Documentation/networking/ |
| H A D | mptcp-sysctl.rst | 87 traffic to propagate all of the related events and commands. 104 traffic to propagate all of the related events and commands.
|
| /linux-6.15/tools/memory-model/Documentation/ |
| H A D | explanation.txt | 857 on C to propagate to C' before any po-later stores do. 861 stores executed on C) is forced to propagate to C' before the 866 propagate to all other CPUs before any instructions po-after 900 and W ->cumul-fence W', then W must propagate to any given CPU 902 require W to propagate to C before W' propagates to C'. 926 Propagation: This requires that certain stores propagate to 1458 propagate to every CPU and to RAM before F executes. 1533 propagates to C's CPU before the end of C must propagate to 1537 propagates to G's CPU before the start of G must propagate 2117 propagate to each CPU before W' does. For example, consider: [all …]
|
| /linux-6.15/drivers/staging/media/deprecated/atmel/ |
| H A D | TODO | 20 media-controller configurable, and will not propagate the formats down to
|
| /linux-6.15/Documentation/admin-guide/hw-vuln/ |
| H A 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-6.15/Documentation/trace/coresight/ |
| H 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
|
| H A D | coresight.rst | 281 as a sink, or as a link to propagate further along the chain:: 658 individual CTIs and components, and can propagate these between all CTIs via
|
| /linux-6.15/tools/memory-model/ |
| H A D | linux-kernel.cat | 56 * propagate to one of the involved CPUs before it hands over the lock to 57 * the next CPU will also propagate to the final CPU handing over the lock
|
| /linux-6.15/Documentation/filesystems/nfs/ |
| H A D | reexport.rst | 20 The "crossmnt" export does not propagate "fsid=", so it will not allow
|
| /linux-6.15/Documentation/admin-guide/cgroup-v1/ |
| H A D | devices.rst | 81 it'll propagate down and after revalidating B's entries, the whitelist entry
|
| /linux-6.15/tools/lib/ |
| H A D | rbtree.c | 428 .propagate = dummy_propagate,
|
| /linux-6.15/lib/ |
| H A D | rbtree.c | 429 .propagate = dummy_propagate,
|
| /linux-6.15/Documentation/admin-guide/ |
| H A D | xfs.rst | 406 Defines how fast XFS should propagate an error upwards when a specific 407 error is found during the filesystem operation. It can propagate 487 the filesystem will propagate the error. The retry count for a given
|
| H A D | sysfs-rules.rst | 177 propagate errors wherever possible. Common errors include, but are not
|
| /linux-6.15/tools/testing/selftests/filesystems/mount-notify/ |
| H A D | mount-notify_test.c | 326 TEST_F(fanotify, propagate) in TEST_F() argument
|
| /linux-6.15/Documentation/arch/x86/ |
| H A D | shstk.rst | 61 feature is enabled on the first thread, it will propagate to all the thread's
|
| /linux-6.15/arch/m68k/fpsp040/ |
| H A D | round.S | 214 addql #1,LOCAL_HI(%a0) |propagate carry 233 addql #1,LOCAL_HI(%a0) |propagate carry
|
| /linux-6.15/Documentation/bpf/ |
| H A D | verifier.rst | 408 In order to propagate information between parent and child states, a *register 486 and stack slots. The main idea of the algorithm is that read marks propagate 529 it be otherwise, the algorithm above wouldn't be able to propagate the read mark
|
| /linux-6.15/scripts/ |
| H A D | spelling.txt | 1294 propigate||propagate 1297 propogate||propagate
|