Home
last modified time | relevance | path

Searched full:negligible (Results 1 – 25 of 45) sorted by relevance

12

/linux/lib/
H A DKconfig.kfence14 to have negligible cost to permit enabling it in production
/linux/Documentation/driver-api/thermal/
H A Dcpu-cooling-api.rst75 negligible. Herein we refer to this as 'utilisation'.
/linux/Documentation/infiniband/
H A Dipoib.rst96 The performance impact of this option is negligible, so it
/linux/drivers/gpu/drm/i915/
H A DKconfig.profile98 take a non-negligible time to setup, we do a short spin first to
/linux/kernel/
H A DKconfig.preempt141 The runtime overhead is negligible with HAVE_STATIC_CALL_INLINE enabled
/linux/arch/mips/kernel/
H A Dsyscall.c50 * the performance advantage is negligible.
/linux/Documentation/admin-guide/mm/
H A Dmultigen_lru.rst49 disabled, the multi-gen LRU will suffer a negligible
/linux/kernel/kcsan/
H A Ddebugfs.c67 * negligible) call into slow-path, but never set up watchpoints. in microbenchmark()
/linux/arch/x86/math-emu/
H A Dpoly_tan.c145 have negligible effect in later calculations in poly_tan()
/linux/include/linux/
H A Drtc.h125 * is negligible. For RTCs behind slow busses the transport time is
H A Dzstd_lib.h1075 * It's also a CPU consuming operation, with non-negligible impact on latency.
1118 * It's a CPU consuming operation, with non-negligible impact on latency.
1133 * which has a non-negligible impact on CPU usage and latency.
3125 …Frame metadata cost is typically ~12 bytes, which can be non-negligible for very small blocks (< 1…
3137 …Frame metadata is not that costly, and quickly becomes negligible as source size grows larger than…
/linux/arch/x86/kvm/vmx/
H A Dposted_intr.c239 * the cost of propagating PIR.IRR to PID.ON is negligible compared to in vmx_vcpu_pi_put()
/linux/Documentation/mm/
H A Dmultigen_lru.rst103 ``folio->flags`` and therefore has a negligible cost. A feedback loop
/linux/tools/testing/selftests/bpf/benchs/
H A Dbench_trigger.c353 /* overhead of function call is negligible compared to uprobe in usetup()
/linux/drivers/pmdomain/
H A Dgovernor.c36 * suspend/resume latencies, so assume them to be negligible and in dev_update_qos_constraint()
/linux/fs/erofs/
H A Dinternal.h375 /* Used to map the whole extent if non-negligible data is requested for LZMA */
/linux/Documentation/core-api/
H A Drbtree.rst203 potentially expensive tree iterations. This is done at negligible runtime
/linux/kernel/sched/
H A Dmembarrier.c199 * is negligible. in ipi_rseq()
/linux/Documentation/process/
H A Dmaintainer-kvm-x86.rst252 negligible probability of affecting runtime behavior, e.g. patches that only
/linux/Documentation/gpu/
H A Ddrm-vm-bind-locking.rst370 associated with this type of iteration is, most likely, negligible. Note that
/linux/drivers/usb/storage/
H A Dscsiglue.c262 * impact is negligible we set this flag for all USB disks in sdev_configure()
/linux/Documentation/admin-guide/
H A Dreporting-regressions.rst320 deal with (often negligible) regressions when a WiFi driver from the staging
/linux/Documentation/networking/
H A Dscaling.rst103 an IRQ may be handled on any CPU. Because a non-negligible part of packet
/linux/kernel/rcu/
H A Dsrcutree.c1205 * negligible when amortized over that time period, and the extra latency in srcu_should_expedite()
1206 * of a needlessly non-expedited grace period is similarly negligible. in srcu_should_expedite()
/linux/Documentation/devicetree/bindings/cpu/
H A Didle-states.yaml93 event conditions. The abort latency is assumed to be negligible

12