| /linux-6.6.21/include/linux/ |
| 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.6.21/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-6.6.21/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-6.6.21/tools/memory-model/litmus-tests/ |
| D | MP+unlocklockonceonce+fencermbonceonce.litmus | 7 * first must propagate to each CPU before stores in the second do, even if
|
| /linux-6.6.21/Documentation/netlink/specs/ |
| D | rt_route.yaml | 166 name: rta-ttl-propagate
297 - rta-ttl-propagate
|
| /linux-6.6.21/Documentation/filesystems/ |
| 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.6.21/tools/memory-model/Documentation/ |
| 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
870 affects stores from other CPUs that propagate to CPU C before the
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
1186 smp_wmb() forces P0's store to x to propagate to P1 before the store
1234 po-earlier stores to propagate to every other CPU in the system; then
1270 for the memory subsystem not to propagate W to R's CPU until after R
[all …]
|
| /linux-6.6.21/drivers/staging/media/deprecated/atmel/ |
| D | TODO | 20 media-controller configurable, and will not propagate the formats down to
|
| /linux-6.6.21/Documentation/networking/ |
| D | mptcp-sysctl.rst | 57 traffic to propagate all of the related events and commands.
|
| /linux-6.6.21/Documentation/admin-guide/hw-vuln/ |
| 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.6.21/tools/memory-model/ |
| D | linux-kernel.cat | 46 * propagate to one of the involved CPUs before it hands over the lock to
47 * the next CPU will also propagate to the final CPU handing over the lock
|
| /linux-6.6.21/Documentation/trace/coresight/ |
| 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
|
| D | coresight.rst | 281 as a sink, or as a link to propagate further along the chain::
663 individual CTIs and components, and can propagate these between all CTIs via
|
| /linux-6.6.21/Documentation/filesystems/nfs/ |
| D | reexport.rst | 20 The "crossmnt" export does not propagate "fsid=", so it will not allow
|
| /linux-6.6.21/tools/lib/ |
| D | rbtree.c | 428 .propagate = dummy_propagate,
|
| /linux-6.6.21/Documentation/admin-guide/cgroup-v1/ |
| D | devices.rst | 81 it'll propagate down and after revalidating B's entries, the whitelist entry
|
| /linux-6.6.21/lib/ |
| D | rbtree.c | 429 .propagate = dummy_propagate,
|
| /linux-6.6.21/Documentation/admin-guide/ |
| D | xfs.rst | 390 Defines how fast XFS should propagate an error upwards when a specific
391 error is found during the filesystem operation. It can propagate
471 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-6.6.21/Documentation/arch/x86/ |
| D | shstk.rst | 61 feature is enabled on the first thread, it will propagate to all the thread's
|
| /linux-6.6.21/arch/m68k/fpsp040/ |
| D | round.S | 214 addql #1,LOCAL_HI(%a0) |propagate carry
233 addql #1,LOCAL_HI(%a0) |propagate carry
|
| /linux-6.6.21/Documentation/bpf/ |
| 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.6.21/scripts/ |
| D | spelling.txt | 1236 propigate||propagate
1239 propogate||propagate
|
| /linux-6.6.21/arch/arm64/boot/dts/allwinner/ |
| D | sun50i-h616.dtsi | 63 * to propagate this into the DTB handed to kernels.
|
| /linux-6.6.21/Documentation/userspace-api/media/v4l/ |
| D | dev-subdev.rst | 185 Drivers automatically propagate formats inside sub-devices. When a try
666 A common way to accomplish this is to start from the sensors and propagate the
|