+9
−1
Loading
If an application doesn't set the power env explicitly, DPDK will just iterate through them one at a time until it finds one that works. This clutters the log with error messages about the ones that didn't work. So use the rte_power_check_env_supported() API to iterate through them ourselves (just like DPDK does) and set the first one that we find. From what I can see, only one can ever work. So SPDK iterates through the DPDK enum in order, even though DPDK does them out of order when it needs to find one because the user didn't set one. While here, set the DPDK rte_power log level to WARNING, which also eliminates a ton of noisy messages when enabling the governor. While adding this, we noticed that cryptodev flag here is setting WARNING but the comment says ERR, so fix that comment while here. Signed-off-by:Jim Harris <jim.harris@samsung.com> Change-Id: I5cb2552d3b41235884577669bd574f88ca944f2a Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/23408 Community-CI: Mellanox Build Bot Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by:
Tomasz Zawadzki <tomasz.zawadzki@intel.com>