Searched full:impact (Results 1 – 25 of 800) sorted by relevance
12345678910>>...32
| /kernel/linux/linux-6.6/security/ |
| D | Kconfig.hardening | 47 variables initialized), but the performance impact depends
173 impact being driven by the depth of the stack usage, rather than
176 The performance impact on a single CPU system kernel compilation
216 can be useful for estimating the STACKLEAK performance impact for
236 heap content exposures. The performance impact varies by
237 workload, but most cases see <1% impact. Some synthetic
253 The performance impact varies by workload, but is more expensive
255 touching "cold" memory areas. Most cases see 3-5% impact. Some
275 image. This has a less than 1% performance impact on most
324 Enabling this feature will introduce some performance impact,
[all …]
|
| /kernel/linux/linux-5.10/security/ |
| D | Kconfig.hardening | 47 variables initialized), but the performance impact depends
168 impact being driven by the depth of the stack usage, rather than
171 The performance impact on a single CPU system kernel compilation
201 can be useful for estimating the STACKLEAK performance impact for
220 heap content exposures. The performance impact varies by
221 workload, but most cases see <1% impact. Some synthetic
236 The performance impact varies by workload, but is more expensive
238 touching "cold" memory areas. Most cases see 3-5% impact. Some
|
| /kernel/linux/linux-5.10/drivers/atm/ |
| D | Kconfig | 60 generally using printks, but still has some impact on performance.
175 generally using printks, but still has some impact on performance.
230 When active, these messages can have a significant impact on the
232 inactive, they will have only a modest impact on performance.
268 When active, these messages can have a significant impact on the
270 inactive, they will have only a modest impact on performance.
292 When active, these messages can have a significant impact on the
294 inactive, they will have only a modest impact on performance.
326 When active, these messages can have a significant impact on the
328 inactive, they will have only a modest impact on performance.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-class-fc_host | 7 performance impact notification (FPIN) event.
15 performance impact notification (FPIN) event.
23 performance impact notification (FPIN) event.
|
| D | sysfs-class-fc_remote_ports | 7 performance impact notification (FPIN) event.
15 performance impact notification (FPIN) event.
23 performance impact notification (FPIN) event.
|
| D | sysfs-class-devlink | 45 This file indicates if the device link has any impact on the
82 and has no impact on the binding, unbinding and syncing the
|
| /kernel/linux/linux-6.6/drivers/zorro/ |
| D | zorro.ids | 118 0800 Impact Series I [SCSI Host Adapter and RAM Expansion]
119 2000 Impact Vision 24 [Graphics Card]
132 0100 Impact Series I (4K) [SCSI Host Adapter]
133 0200 Impact Series I (16K/2) [SCSI Host Adapter]
134 0300 Impact Series I (16K/2) [SCSI Host Adapter]
135 0800 Impact 3001 [IDE Interface]
136 0900 Impact 3001 [RAM Expansion]
137 0a00 Impact Series II [RAM Expansion]
152 0d00 Impact 3001 [IDE Interface]
154 2000 Impact Vision 24 [Graphics Card]
[all …]
|
| /kernel/linux/linux-5.10/drivers/zorro/ |
| D | zorro.ids | 118 0800 Impact Series I [SCSI Host Adapter and RAM Expansion]
119 2000 Impact Vision 24 [Graphics Card]
132 0100 Impact Series I (4K) [SCSI Host Adapter]
133 0200 Impact Series I (16K/2) [SCSI Host Adapter]
134 0300 Impact Series I (16K/2) [SCSI Host Adapter]
135 0800 Impact 3001 [IDE Interface]
136 0900 Impact 3001 [RAM Expansion]
137 0a00 Impact Series II [RAM Expansion]
152 0d00 Impact 3001 [IDE Interface]
154 2000 Impact Vision 24 [Graphics Card]
[all …]
|
| /kernel/linux/linux-6.6/drivers/atm/ |
| D | Kconfig | 60 generally using printks, but still has some impact on performance.
200 When active, these messages can have a significant impact on the
202 inactive, they will have only a modest impact on performance.
247 When active, these messages can have a significant impact on the
249 inactive, they will have only a modest impact on performance.
300 When active, these messages can have a significant impact on
|
| /kernel/linux/linux-6.6/drivers/staging/iio/accel/ |
| D | Kconfig | 20 tristate "Analog Devices ADIS16240 Programmable Impact Sensor and Recorder"
26 impact Sensor and recorder.
|
| /kernel/linux/linux-5.10/drivers/staging/iio/accel/ |
| D | Kconfig | 20 tristate "Analog Devices ADIS16240 Programmable Impact Sensor and Recorder"
26 impact Sensor and recorder.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/accel/ |
| D | adi,adis16240.yaml | 7 title: ADIS16240 Programmable Impact Sensor and Recorder driver
13 ADIS16240 Programmable Impact Sensor and Recorder driver that supports
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/iio/accel/ |
| D | adi,adis16240.yaml | 7 title: ADIS16240 Programmable Impact Sensor and Recorder driver
13 ADIS16240 Programmable Impact Sensor and Recorder driver that supports
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/hw-vuln/ |
| D | l1tf.rst | 80 impact. The kernel ensures that the address bits of PTEs, which are not
111 deployment scenario. The mitigations, their protection scope and impact
178 data. Flushing the L1D has a performance impact as the processor has to
182 scenarios where guest VMEXIT/VMENTER are rare the performance impact is
279 completely. Disabling SMT can have a significant performance impact, but
280 the impact depends on the hosting scenario and the type of workloads.
281 The impact of disabling SMT needs also to be weighted against the impact
354 significant performance impact especially when the Meltdown mitigation
360 address the performance impact of disabling SMT or EPT.
547 enabled and L1D flushing is not required, but the performance impact is
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/hw-vuln/ |
| D | l1tf.rst | 80 impact. The kernel ensures that the address bits of PTEs, which are not
111 deployment scenario. The mitigations, their protection scope and impact
178 data. Flushing the L1D has a performance impact as the processor has to
182 scenarios where guest VMEXIT/VMENTER are rare the performance impact is
279 completely. Disabling SMT can have a significant performance impact, but
280 the impact depends on the hosting scenario and the type of workloads.
281 The impact of disabling SMT needs also to be weighted against the impact
354 significant performance impact especially when the Meltdown mitigation
360 address the performance impact of disabling SMT or EPT.
547 enabled and L1D flushing is not required, but the performance impact is
|
| /kernel/linux/linux-6.6/Documentation/accel/qaic/ |
| D | qaic.rst | 64 Major number updates indicate changes to the NNC protocol which impact the
67 Minor number updates indicate changes to the NNC protocol which impact the
68 commands (does not impact QAIC).
|
| /kernel/linux/linux-5.10/drivers/cpuidle/governors/ |
| D | menu.c | 35 * 2) Performance impact
59 * seconds of idle time. A second independent factor that has big impact on
78 * Limiting Performance Impact
81 * noticeable impact on workloads, which is not acceptable for most sysadmins,
86 * The busier the system, the less impact of C states is acceptable
91 * for selection due to a too high performance impact. So the higher
|
| /kernel/linux/linux-6.6/Documentation/scheduler/ |
| D | sched-energy.rst | 9 the impact of its decisions on the energy consumed by CPUs. EAS relies on an
11 with a minimal impact on throughput. This document aims at providing an
57 impact.
264 running on a little, but it won't impact the other tasks of the little CPUs
274 impact on throughput for high-utilization scenarios, EAS also implements another
345 EAS uses the EM of a platform to estimate the impact of scheduling decisions on
|
| /kernel/linux/linux-6.6/drivers/cpuidle/governors/ |
| D | menu.c | 37 * 2) Performance impact
61 * seconds of idle time. A second independent factor that has big impact on
80 * Limiting Performance Impact
83 * noticeable impact on workloads, which is not acceptable for most sysadmins,
88 * The busier the system, the less impact of C states is acceptable
93 * for selection due to a too high performance impact. So the higher
|
| /kernel/linux/linux-5.10/Documentation/scheduler/ |
| D | sched-energy.rst | 9 the impact of its decisions on the energy consumed by CPUs. EAS relies on an
11 with a minimal impact on throughput. This document aims at providing an
57 impact.
264 running on a little, but it won't impact the other tasks of the little CPUs
274 impact on throughput for high-utilization scenarios, EAS also implements another
345 EAS uses the EM of a platform to estimate the impact of scheduling decisions on
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | cleancache.rst | 143 with a fairly small impact on the kernel, provide a huge amount
187 The total impact of the hooks to existing fs and mm files is only
215 * What's the performance impact?
281 time, but have insignificant performance impact when cleancache remains
|
| /kernel/linux/linux-6.6/arch/arm64/kernel/ |
| D | Makefile | 18 # can significantly impact performance. Avoid instrumenting the stack trace
19 # collection code to minimize this impact.
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-devlink | 45 This file indicates if the device link has any impact on the
82 and has no impact on the binding, unbinding and syncing the
|
| /kernel/linux/linux-5.10/kernel/livepatch/ |
| D | Kconfig | 17 This option has no runtime impact until a kernel "patch"
|
| /kernel/linux/linux-6.6/kernel/livepatch/ |
| D | Kconfig | 17 This option has no runtime impact until a kernel "patch"
|
12345678910>>...32