| /linux/security/ |
| H A D | Kconfig.hardening | 30 variables initialized), but the performance impact depends
101 impact being driven by the depth of the stack usage, rather than
104 The performance impact on a single CPU system kernel compilation
148 can be useful for estimating the KSTACK_ERASE performance impact
168 heap content exposures. The performance impact varies by
169 workload, but most cases see <1% impact. Some synthetic
185 The performance impact varies by workload, but is more expensive
187 touching "cold" memory areas. Most cases see 3-5% impact. Some
205 image. This has a less than 1% performance impact on most
292 Enabling this feature will introduce some performance impact,
[all …]
|
| /linux/drivers/zorro/ |
| H A 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 …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-fc_host | 7 performance impact notification (FPIN) event.
15 performance impact notification (FPIN) event.
23 performance impact notification (FPIN) event.
|
| H A D | sysfs-class-fc_remote_ports | 7 performance impact notification (FPIN) event.
15 performance impact notification (FPIN) event.
23 performance impact notification (FPIN) event.
|
| H A 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
|
| /linux/tools/perf/pmu-events/arch/x86/sierraforest/ |
| H A D | uncore-interconnect.json | 1099 "BriefDescription": "Valid Flits Received : All Data : Shows legal flit time (hides impact of L0p and L0c).",
1119 "BriefDescription": "Valid Flits Received : Data : Shows legal flit time (hides impact of L0p and L0c). : Count Data Flits (which consume all slots), but how much to count is based on Slot0-2 mask, so count can be 0-3 depending on which slots are enabled for counting..",
1129 "BriefDescription": "Valid Flits Received : Idle : Shows legal flit time (hides impact of L0p and L0c).",
1139 "BriefDescription": "Valid Flits Received : LLCRD Not Empty : Shows legal flit time (hides impact of L0p and L0c). : Enables counting of LLCRD (with non-zero payload). This only applies to slot 2 since LLCRD is only allowed in slot 2",
1149 "BriefDescription": "Valid Flits Received : LLCTRL : Shows legal flit time (hides impact of L0p and L0c). : Equivalent to an idle packet. Enables counting of slot 0 LLCTRL messages.",
1159 "BriefDescription": "Valid Flits Received : All Non Data : Shows legal flit time (hides impact of L0p and L0c).",
1168 "BriefDescription": "Valid Flits Received : Slot NULL or LLCRD Empty : Shows legal flit time (hides impact of L0p and L0c). : LLCRD with all zeros is treated as NULL. Slot 1 is not treated as NULL if slot 0 is a dual slot. This can apply to slot 0,1, or 2.",
1178 "BriefDescription": "Valid Flits Received : Protocol Header : Shows legal flit time (hides impact of L0p and L0c). : Enables count of protocol headers in slot 0,1,2 (depending on slot uMask bits)",
1188 "BriefDescription": "Valid Flits Received : Slot 0 : Shows legal flit time (hides impact of L0p and L0c). : Count Slot 0 - Other mask bits determine types of headers to count.",
1198 "BriefDescription": "Valid Flits Received : Slot 1 : Shows legal flit time (hides impact o
[all...] |
| /linux/tools/perf/pmu-events/arch/x86/graniterapids/ |
| H A D | uncore-interconnect.json | 1453 "BriefDescription": "Valid Flits Received : All Data : Shows legal flit time (hides impact of L0p and L0c).",
1473 "BriefDescription": "Valid Flits Received : Data : Shows legal flit time (hides impact of L0p and L0c). : Count Data Flits (which consume all slots), but how much to count is based on Slot0-2 mask, so count can be 0-3 depending on which slots are enabled for counting..",
1483 "BriefDescription": "Valid Flits Received : Idle : Shows legal flit time (hides impact of L0p and L0c).",
1493 "BriefDescription": "Valid Flits Received : LLCRD Not Empty : Shows legal flit time (hides impact of L0p and L0c). : Enables counting of LLCRD (with non-zero payload). This only applies to slot 2 since LLCRD is only allowed in slot 2",
1503 "BriefDescription": "Valid Flits Received : LLCTRL : Shows legal flit time (hides impact of L0p and L0c). : Equivalent to an idle packet. Enables counting of slot 0 LLCTRL messages.",
1513 "BriefDescription": "Valid Flits Received : All Non Data : Shows legal flit time (hides impact of L0p and L0c).",
1522 "BriefDescription": "Valid Flits Received : Slot NULL or LLCRD Empty : Shows legal flit time (hides impact of L0p and L0c). : LLCRD with all zeros is treated as NULL. Slot 1 is not treated as NULL if slot 0 is a dual slot. This can apply to slot 0,1, or 2.",
1532 "BriefDescription": "Valid Flits Received : Protocol Header : Shows legal flit time (hides impact of L0p and L0c). : Enables count of protocol headers in slot 0,1,2 (depending on slot uMask bits)",
1542 "BriefDescription": "Valid Flits Received : Slot 0 : Shows legal flit time (hides impact of L0p and L0c). : Count Slot 0 - Other mask bits determine types of headers to count.",
1552 "BriefDescription": "Valid Flits Received : Slot 1 : Shows legal flit time (hides impact o
[all...] |
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A 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
|
| /linux/Documentation/scheduler/ |
| H A 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
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | zswap.rst | 18 performance impact of swapping.
22 impact to the guest workload and guests sharing the I/O subsystem
|
| H A D | multigen_lru.rst | 67 cause janks (lags when rendering UI) and negatively impact user
97 in a given time interval, and it is usually done with little impact on
|
| /linux/Documentation/arch/powerpc/ |
| H A D | qe_firmware.rst | 120 which has an impact on the software drivers. Each bit has its own impact
233 impact on the device drivers. Each bit has its own impact and has special
|
| /linux/arch/parisc/ |
| H A D | Kconfig.debug | 8 Add checks with low performance impact to the spinlock functions
|
| /linux/tools/perf/util/bpf_skel/ |
| H A D | bperf_cgroup.h | 6 // These constants impact code size of bperf_cgroup.bpf.c that may result in BPF
|
| /linux/Documentation/core-api/real-time/ |
| H A D | kernel-configuration.rst | 95 significantly impact hardware longevity, warranty, and thermal behavior.
248 These options increase the kernel image size but have no latency impact. They
265 impact, but beware of any debug features that it may have implicitly enabled.
|
| /linux/tools/testing/vma/tests/ |
| H A D | merge.c | 328 vma_a->vm_ops = &vm_ops; /* This should have no impact. */ in __test_merge_new()
370 vma_d->vm_ops = &vm_ops; /* This should have no impact. */ in __test_merge_new()
871 vma->vm_ops = &vm_ops; /* This should have no impact. */ in __test_merge_existing()
873 vma_next->vm_ops = &vm_ops; /* This should have no impact. */ in __test_merge_existing()
910 vma_next->vm_ops = &vm_ops; /* This should have no impact. */ in __test_merge_existing()
940 vma_prev->vm_ops = &vm_ops; /* This should have no impact. */ in __test_merge_existing()
942 vma->vm_ops = &vm_ops; /* This should have no impact. */ in __test_merge_existing()
978 vma_prev->vm_ops = &vm_ops; /* This should have no impact. */ in __test_merge_existing()
1010 vma_prev->vm_ops = &vm_ops; /* This should have no impact. */ in __test_merge_existing()
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | bpf_compiler.h | 11 same impact than the loop-unroll-enable pragma above. */
|
| /linux/drivers/infiniband/hw/hfi1/ |
| H A D | aspm.h | 28 /* Quickest exit for minimum impact */ in aspm_ctx_disable()
|
| /linux/fs/ocfs2/ |
| H A D | dcache.h | 22 * ->d_iput() anyway, so there should be minimal impact.
|
| /linux/arch/alpha/include/uapi/asm/ |
| H A D | types.h | 15 * and we don't want to impact user mode with our change to ll64
|
| /linux/Documentation/accounting/ |
| H A D | psi.rst | 19 such resource crunches and the time impact it has on complex workloads
52 severe impact on performance, and it's useful to distinguish this
|
| /linux/arch/mips/include/asm/xtalk/ |
| H A D | xwidget.h | 97 #define WIDGET_IMPCT_MFGR_NUM 0x2aa /* HQ4 / Impact GFX */
146 "impact",
|
| /linux/drivers/net/ethernet/myricom/ |
| H A D | Kconfig | 43 is used, with the intent of lessening the impact of cache misses.
|
| /linux/Documentation/power/regulator/ |
| H A D | design.rst | 6 of the design considerations which impact the regulator API design.
|
| /linux/arch/powerpc/include/uapi/asm/ |
| H A D | types.h | 19 * and we don't want to impact user mode with our change to ll64
|