Hi Slava, Le 20/03/26 15:38, Slava Ovsiienko a écrit : > BTW, we have mlx5_tx_burst_mode_get(), all information about tx rate limit > could be shown there. > (I do not insist on, JFYI).
Thank you for the suggestion. But I think keeping both makes sense for different use cases: - mlx5_tx_burst_mode_get(), it returns a human-readable string describing the burst mode. Embedding rate limit info there would mix concerns and the information would only be available as unstructured text. - rte_pmd_mlx5_txq_rate_limit_query() returns some structured data (rate_mbps, pp_index, fw_pp_index) that the applications and scripts can consume programmatically. The readback via mlx5_devx_cmd_query_sq() is also useful for verifying that the firmware actually applied the PP index to the SQ. Best regards, Vincent
