Searched full:implies (Results 1 – 25 of 1479) sorted by relevance
12345678910>>...60
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | virtual-memory.json | 6 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
31 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
39 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
47 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
55 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
71 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
96 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
104 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
112 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
120 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/skylake/ |
| D | virtual-memory.json | 6 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
31 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
39 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
47 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
55 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
71 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
96 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
104 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
112 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
120 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | virtual-memory.json | 6 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
31 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
39 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
47 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
55 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
71 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
96 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
104 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
112 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
120 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| D | virtual-memory.json | 23 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
31 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
39 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
47 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
80 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
88 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
96 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
104 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
137 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
145 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/icelakex/ |
| D | virtual-memory.json | 23 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
31 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
39 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
47 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
80 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
88 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
96 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
104 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
137 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
145 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/alderlake/ |
| D | virtual-memory.json | 34 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
43 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
52 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
61 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
107 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
116 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
125 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
134 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
196 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
205 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/rocketlake/ |
| D | virtual-memory.json | 23 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
31 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
39 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
72 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
80 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
88 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
121 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
129 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
137 …Counts completed page walks (4K page sizes) caused by a code fetch. This implies it missed in the …
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/icelake/ |
| D | virtual-memory.json | 23 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
31 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
39 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
72 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
80 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
88 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
121 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
129 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
137 …Counts completed page walks (4K page sizes) caused by a code fetch. This implies it missed in the …
|
| /kernel/linux/linux-5.10/arch/xtensa/include/asm/ |
| D | asm-uaccess.h | 72 * <success>. This implies that the macro falls through to the next
81 * <success> label to branch to on success; implies
101 * <error>. This implies that the macro falls through to the next
112 * <error> label to branch to on error; implies fall-through
131 * <error>. This implies that the macro falls through to the next
142 * <error> label to branch to on error; implies fall-through
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/meteorlake/ |
| D | virtual-memory.json | 41 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
50 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
68 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
77 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
139 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
148 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
157 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
166 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
237 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
255 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/tigerlake/ |
| D | virtual-memory.json | 23 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
31 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
39 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
72 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
121 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
129 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
137 …Counts completed page walks (4K page sizes) caused by a code fetch. This implies it missed in the …
|
| /kernel/linux/linux-6.6/arch/xtensa/include/asm/ |
| D | asm-uaccess.h | 31 * <error>. This implies that the macro falls through to the next
42 * <error> label to branch to on error; implies fall-through
61 * <error>. This implies that the macro falls through to the next
72 * <error> label to branch to on error; implies fall-through
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | virtual-memory.json | 13 …ts when a data (D) page walk is completed or started. Since a page walk implies a TLB miss, the n…
32 …an instruction (I) page walk is completed or started. Since a page walk implies a TLB miss, the n…
51 …an instruction (I) page walk is completed or started. Since a page walk implies a TLB miss, the n…
61 …page walk or instruction (I) page walk is in progress. Since a pagewalk implies a TLB miss, the a…
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | virtual-memory.json | 15 …page walk or instruction (I) page walk is in progress. Since a pagewalk implies a TLB miss, the a…
32 …ts when a data (D) page walk is completed or started. Since a page walk implies a TLB miss, the n…
49 …an instruction (I) page walk is completed or started. Since a page walk implies a TLB miss, the n…
58 …an instruction (I) page walk is completed or started. Since a page walk implies a TLB miss, the n…
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/graniterapids/ |
| D | virtual-memory.json | 6 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
14 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
22 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
|
| /kernel/linux/linux-5.10/tools/testing/selftests/android/ion/ |
| D | ipcsocket.h | 20 * name: implies a unique socket name in the system
21 * connecttype: implies server(0) or client(1)
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/skylake/ |
| D | virtual-memory.json | 3 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
43 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
84 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
124 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
175 …s page walks of any page size (4K/2M/4M/1G) caused by a code fetch. This implies it missed in the …
185 …"Counts completed page walks (4K page size) caused by a code fetch. This implies it missed in the …
215 …completed page walks (2M and 4M page sizes) caused by a code fetch. This implies it missed in the …
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | virtual-memory.json | 28 …completed page walks (2M and 4M page sizes) caused by a code fetch. This implies it missed in the …
38 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
79 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
160 …s page walks of any page size (4K/2M/4M/1G) caused by a code fetch. This implies it missed in the …
180 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
200 …"Counts completed page walks (4K page size) caused by a code fetch. This implies it missed in the …
249 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | virtual-memory.json | 17 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
47 …"Counts completed page walks (4K page size) caused by a code fetch. This implies it missed in the …
129 …s page walks of any page size (4K/2M/4M/1G) caused by a code fetch. This implies it missed in the …
149 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
159 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
189 …completed page walks (2M and 4M page sizes) caused by a code fetch. This implies it missed in the …
219 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
|
| /kernel/linux/linux-6.6/arch/x86/include/asm/ |
| D | sync_bitops.h | 81 * It also implies a memory barrier.
94 * It also implies a memory barrier.
107 * It also implies a memory barrier.
|
| /kernel/linux/linux-5.10/arch/x86/include/asm/ |
| D | sync_bitops.h | 81 * It also implies a memory barrier.
94 * It also implies a memory barrier.
107 * It also implies a memory barrier.
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/powerpc/power10/ |
| D | frontend.json | 5 …"BriefDescription": "Data TLB hit (DERAT reload) page size 2M. Implies radix translation. When MMC…
55 …"BriefDescription": "Instruction TLB hit (IERAT reload) page size 1G, which implies Radix Page Tab…
85 …"BriefDescription": "Data TLB hit (DERAT reload) page size 1G. Implies radix translation. When MMC…
|
| /kernel/linux/linux-6.6/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | counters.rst | 919 on a physical port. If this counter is increasing, it implies that the
926 size on a physical port. If this counter is increasing, it implies that
946 this counter is increasing, it implies that the network is congested and
952 this counter is increasing, it implies that the NIC is congested and
963 physical port. If this counter is increasing, it implies that the adapter
981 implies that the peer connected to the adapter has a non-standard MTU
988 increasing, it implies that the peer connected to the adapter has a
1107 interface. If this counter is increasing, it implies that the link
1116 (RS/FC). If this counter is increasing, it implies that the link between
1125 increasing, it implies that the link between the NIC and the network is
[all …]
|
| /kernel/linux/linux-6.6/arch/mips/include/asm/ |
| D | bitops.h | 139 * clear_bit() is atomic and implies release semantics before the memory
175 * This operation is atomic and implies acquire ordering semantics
205 * It also implies a memory barrier.
220 * It also implies a memory barrier.
257 * It also implies a memory barrier.
292 * __clear_bit() is non-atomic and implies release semantics before the memory
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/ |
| D | bitops.h | 141 * clear_bit() is atomic and implies release semantics before the memory
177 * This operation is atomic and implies acquire ordering semantics
207 * It also implies a memory barrier.
222 * It also implies a memory barrier.
259 * It also implies a memory barrier.
294 * __clear_bit() is non-atomic and implies release semantics before the memory
|
12345678910>>...60