On 2024/9/10 17:32, lihuisong (C) wrote:
> Hi Chengwen,
> 
> Thanks for your review.
> 
> 在 2024/9/10 10:00, fengchengwen 写道:
>> Hi Huisong
>>
>> Please see comments inline.
>>
>> Thanks
>>
>> On 2024/8/9 17:50, Huisong Li wrote:
>>> 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. 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).
>>>
>>> Signed-off-by: Huisong Li <lihuis...@huawei.com>
>>> Acked-by: Morten Brørup <m...@smartsharesystems.com>
>>> ---
>> ...
>>

...

>>> diff --git a/lib/power/version.map b/lib/power/version.map
>>> index c9a226614e..4e4955a4cf 100644
>>> --- a/lib/power/version.map
>>> +++ b/lib/power/version.map
>>> @@ -51,4 +51,8 @@ EXPERIMENTAL {
>>>       rte_power_set_uncore_env;
>>>       rte_power_uncore_freqs;
>>>       rte_power_unset_uncore_env;
>>> +
>>> +    # added in 24.11
>>> +    rte_power_qos_set_cpu_resume_latency;
>>> +    rte_power_qos_get_cpu_resume_latency;
>> order by alphabetic.
> Ack
>>
>> another question, I think rename cpu with core maybe more accurate, despite 
>> sysfs export with cpu, but in DPDK it means core.
>> and there are some rte_power_core_xxx name in rte_power library, I think 
>> better to keep the same.
> Firstly, the rte_power_qos_set/get_cpu_resume_latency is just consistent with 
> linux sysfs interface. Having the same name is more releative for user.
> In addition, Sivaprasad Tummala is reworking power library and the name of 
> rte_power_core_xxx also might be changed.

ok

>>
>>>   };
>>>
>> .

Reply via email to