> From: Huisong Li [mailto:lihuis...@huawei.com] > Sent: Wednesday, 19 June 2024 08.32 > > The deeper the idle state, the lower the power consumption, but the longer > the resume time. Some service are delay sensitive and very except the low > resume time, like interrupt packet receiving mode. > > And the "/sys/devices/system/cpu/cpuX/power/pm_qos_resume_latency_us" sysfs > interface is used to set and get the resume latency limit on the cpuX for > userspace. Please see the description in kernel document[1]. > Each cpuidle governor in Linux select which idle state to enter based on > this CPU resume latency in their idle task. > > The per-CPU PM QoS API can be used to control this CPU's idle state > selection and limit just enter the shallowest idle state to low the delay > after sleep by setting strict resume latency (zero value). > > [1] https://www.kernel.org/doc/html/latest/admin-guide/abi- > testing.html?highlight=pm_qos_resume_latency_us#abi-sys-devices-power-pm-qos- > resume-latency-us > > --- > v3: > - add RTE_POWER_xxx prefix for some macro in header > - add the check for lcore_id with rte_lcore_is_enabled > v2: > - use PM QoS on CPU wide to replace the one on system wide
Series-acked-by: Morten Brørup <m...@smartsharesystems.com>
