Searched full:negligible (Results 1 – 25 of 57) sorted by relevance
123
| /linux-6.14.4/lib/ |
| D | Kconfig.kfence | 14 to have negligible cost to permit enabling it in production
|
| /linux-6.14.4/Documentation/driver-api/thermal/ |
| D | cpu-cooling-api.rst | 75 negligible. Herein we refer to this as 'utilisation'.
|
| /linux-6.14.4/drivers/gpu/drm/i915/ |
| D | Kconfig.profile | 98 take a non-negligible time to setup, we do a short spin first to
|
| /linux-6.14.4/Documentation/infiniband/ |
| D | ipoib.rst | 96 The performance impact of this option is negligible, so it
|
| /linux-6.14.4/kernel/ |
| D | Kconfig.preempt | 128 The runtime overhead is negligible with HAVE_STATIC_CALL_INLINE enabled
|
| /linux-6.14.4/arch/mips/kernel/ |
| D | syscall.c | 50 * the performance advantage is negligible.
|
| /linux-6.14.4/Documentation/admin-guide/mm/ |
| D | multigen_lru.rst | 49 disabled, the multi-gen LRU will suffer a negligible
|
| /linux-6.14.4/kernel/kcsan/ |
| D | debugfs.c | 67 * negligible) call into slow-path, but never set up watchpoints. in microbenchmark()
|
| /linux-6.14.4/arch/arm64/lib/ |
| D | memcpy.S | 53 check is negligible since it is only required for large copies.
|
| /linux-6.14.4/arch/x86/math-emu/ |
| D | poly_tan.c | 145 have negligible effect in later calculations in poly_tan()
|
| /linux-6.14.4/include/linux/ |
| D | rtc.h | 125 * is negligible. For RTCs behind slow busses the transport time is
|
| D | zstd_lib.h | 943 * It's also a CPU consuming operation, with non-negligible impact on latency.
981 * It's a CPU consuming operation, with non-negligible impact on latency.
996 * which has a non-negligible impact on CPU usage and latency.
2518 …Frame metadata cost is typically ~12 bytes, which can be non-negligible for very small blocks (< 1…
2531 …Frame metadata is not that costly, and quickly becomes negligible as source size grows larger than…
|
| /linux-6.14.4/Documentation/mm/ |
| D | multigen_lru.rst | 103 ``folio->flags`` and therefore has a negligible cost. A feedback loop
|
| /linux-6.14.4/drivers/pmdomain/ |
| D | governor.c | 35 * suspend/resume latencies, so assume them to be negligible and in dev_update_qos_constraint()
|
| /linux-6.14.4/drivers/cxl/core/ |
| D | pci.c | 987 * LinkProgationLatency is negligible, so 0 will be used
988 * RetimerLatency is assumed to be negligible and 0 will be used
|
| /linux-6.14.4/tools/testing/selftests/bpf/benchs/ |
| D | bench_trigger.c | 294 /* overhead of function call is negligible compared to uprobe in uprobe_target_push()
|
| /linux-6.14.4/Documentation/dev-tools/kunit/ |
| D | usage.rst | 733 so will have a negligible performance impact when no test is running.
810 have a negligible performance impact when no test is running.
|
| /linux-6.14.4/fs/erofs/ |
| D | internal.h | 343 /* Used to map the whole extent if non-negligible data is requested for LZMA */
|
| /linux-6.14.4/Documentation/core-api/ |
| D | rbtree.rst | 203 potentially expensive tree iterations. This is done at negligible runtime
|
| /linux-6.14.4/Documentation/filesystems/ |
| D | ramfs-rootfs-initramfs.rst | 35 an optional component removable via menuconfig, since there would be negligible
|
| /linux-6.14.4/Documentation/dev-tools/ |
| D | kcsan.rst | 336 longs to encode watchpoint information, which is negligible.
|
| /linux-6.14.4/kernel/sched/ |
| D | membarrier.c | 197 * is negligible. in ipi_rseq()
|
| /linux-6.14.4/Documentation/process/ |
| D | maintainer-kvm-x86.rst | 252 negligible probability of affecting runtime behavior, e.g. patches that only
|
| /linux-6.14.4/drivers/power/supply/ |
| D | cw2015_battery.c | 324 * Negligible error of 0.1% in cw_get_voltage()
|
| /linux-6.14.4/Documentation/networking/ |
| D | scaling.rst | 96 an IRQ may be handled on any CPU. Because a non-negligible part of packet
|
123