Searched refs:barriers (Results 1 – 25 of 75) sorted by relevance
123
| /linux-6.12.1/Documentation/core-api/wrappers/ |
| D | memory-barriers.rst | 2 This is a simple wrapper to bring memory-barriers.txt into the RST world
6 Linux kernel memory barriers
13 .. include:: ../../memory-barriers.txt
|
| /linux-6.12.1/tools/testing/selftests/bpf/benchs/ |
| D | bench_htab_mem.c | 106 pthread_barrier_t *barriers; in htab_mem_bench_init_barriers() local
113 barriers = calloc(nr, sizeof(*barriers)); in htab_mem_bench_init_barriers()
114 if (!barriers) in htab_mem_bench_init_barriers()
119 pthread_barrier_init(&barriers[i], NULL, 2); in htab_mem_bench_init_barriers()
121 ctx.notify = barriers; in htab_mem_bench_init_barriers()
|
| /linux-6.12.1/Documentation/translations/ko_KR/core-api/wrappers/ |
| D | memory-barriers.rst | 2 This is a simple wrapper to bring memory-barriers.txt into the RST world
13 .. include:: ../../memory-barriers.txt
|
| /linux-6.12.1/Documentation/translations/sp_SP/wrappers/ |
| D | memory-barriers.rst | 2 This is a simple wrapper to bring memory-barriers.txt (Spanish
14 .. include:: ../memory-barriers.txt
|
| /linux-6.12.1/Documentation/ |
| D | memory-barriers.txt | 16 meant as a guide to using the various memory barriers provided by Linux, but
31 (2) to provide a guide as to how to use the barriers that are available.
51 (*) What are memory barriers?
54 - What may not be assumed about memory barriers?
55 - Address-dependency barriers (historical).
59 - Read memory barriers vs load speculation.
62 (*) Explicit kernel barriers.
65 - CPU memory barriers.
67 (*) Implicit kernel memory barriers.
78 (*) Where are memory barriers needed?
[all …]
|
| D | atomic_t.txt | 160 ORDERING (go read memory-barriers.txt first)
188 The barriers:
193 ordering inherent to the op. These barriers act almost like a full smp_mb():
201 These helper barriers exist because architectures have varying implicit
203 provide full ordered atomics and these barriers are no-ops.
|
| D | atomic_bitops.txt | 68 the same barriers as for atomic_t are used, see atomic_t.txt.
|
| /linux-6.12.1/Documentation/translations/zh_CN/core-api/ |
| D | refcount-vs-atomic.rst | 28 memory-barriers.txt和atomic_t.txt提供了更多关于内存顺序的背景，包括通用的
35 序类型。如果想了解更广泛的情况，请查阅memory-barriers.txt文件。
|
| D | circular-buffers.rst | 210 关于Linux的内存屏障设施的描述，请查看Documentation/memory-barriers.txt。
|
| /linux-6.12.1/Documentation/scheduler/ |
| D | membarrier.rst | 10 Memory barriers before updating rq->curr
20 Memory barriers after updating rq->curr
|
| /linux-6.12.1/Documentation/translations/ko_KR/ |
| D | index.rst | 15 core-api/wrappers/memory-barriers.rst
|
| /linux-6.12.1/Documentation/core-api/ |
| D | circular-buffers.rst | 15 (2) Memory barriers for when the producer and the consumer of objects in the
29 (*) Using memory barriers with circular buffers.
134 Using memory barriers with circular buffers
137 By using memory barriers in conjunction with circular buffers, you can avoid
236 See also Documentation/memory-barriers.txt for a description of Linux's memory
|
| D | refcount-vs-atomic.rst | 22 memory-barriers.txt and atomic_t.txt provide more background to the
31 please consult memory-barriers.txt document.
69 barriers, but rely on CPU not to speculate on stores. This is only
|
| D | index.rst | 78 wrappers/memory-barriers.rst
|
| /linux-6.12.1/Documentation/translations/zh_CN/ |
| D | glossary.rst | 25 * memory barriers: 内存屏障。
|
| /linux-6.12.1/tools/memory-model/litmus-tests/ |
| D | R+fencembonceonces.litmus | 8 * propagation delays. Note that weakening either of the barriers would
|
| D | SB+fencembonceonces.litmus | 6 * This litmus test demonstrates that full memory barriers suffice to
|
| /linux-6.12.1/Documentation/RCU/ |
| D | lockdep.rst | 61 Use explicit check expression "c", and omit all barriers
66 Return the value of the pointer and omit all barriers,
101 all barriers and compiler constraints, it generates better code than do
|
| /linux-6.12.1/Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 179 [memory-barriers]_.
182 the memory barriers, allowing this requirement to be handled internally by
205 This solution also requires memory barriers to be placed carefully in both
206 the requesting thread and the receiving VCPU. With the memory barriers we
293 .. [memory-barriers] Documentation/memory-barriers.txt
|
| /linux-6.12.1/Documentation/translations/zh_CN/locking/ |
| D | spinlocks.rst | 33 Documentation/memory-barriers.txt
|
| /linux-6.12.1/Documentation/translations/zh_CN/arch/arm64/ |
| D | legacy_instructions.txt | 42 它是那些构架中正在被淘汰的指令，如 CP15 barriers（隔离指令），的默认处理方式。
|
| /linux-6.12.1/Documentation/translations/zh_TW/arch/arm64/ |
| D | legacy_instructions.txt | 46 它是那些構架中正在被淘汰的指令，如 CP15 barriers（隔離指令），的默認處理方式。
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | ext4.rst | 56 note that ext4 enables write barriers by default, while ext3 does
57 not enable write barriers by default. So it is useful to use
58 explicitly specify whether barriers are enabled or not when via the
59 '-o barriers=[0|1]' mount option for both ext3 and ext4 filesystems
199 This enables/disables the use of write barriers in the jbd code.
201 which can support barriers, and if jbd gets an error on a barrier
202 write, it will disable again with a warning. Write barriers enforce
205 battery-backed in one way or another, disabling barriers may safely
207 also be used to enable or disable barriers, for consistency with other
|
| /linux-6.12.1/Documentation/dev-tools/ |
| D | kcsan.rst | 218 barriers. With ``CONFIG_KCSAN_WEAK_MEMORY=y``, KCSAN models load or store
221 implied barriers.
284 KCSAN's approach to detecting data races due to missing memory barriers is
314 ``flag``, a data race is detected. With the correct barriers in place, ``x``
319 subset of data races due to missing memory barriers can be detected. With
|
| /linux-6.12.1/Documentation/arch/arm64/ |
| D | legacy_instructions.rst | 27 instructions, .e.g., CP15 barriers
|
123