This is a follow up on previous work by Kevin Laatz: http://patches.dpdk.org/project/dpdk/list/?series=24658&state=*
This series is aimed at allowing DPDK applications to expose their CPU usage stats in the DPDK telemetry under /eal/lcore/info. This is a much more basic and naive approach which leaves the cpu cycles accounting completely up to the application. For reference, I have implemented a draft patch in OvS to use rte_lcore_register_usage_cb() and report the already available busy cycles information. https://github.com/rjarry/ovs/commit/643e672fe388e348ea7ccbbda6f5a87a066fd919 v10: - Code style fix - Fixed reset of total_cycles while lcore is running v9: - Fixed changelog & version.map order. - Updated with 64-bit integer telemetry functions. - Refined docstrings (added notice about resetting the callback). - Fixed accounting of total cycles in testpmd. Robin Jarry (5): eal: add lcore info in telemetry eal: report applications lcore usage app/testpmd: add dump command for lcores app/testpmd: report lcore usage eal: add lcore usage telemetry endpoint app/test-pmd/cmdline.c | 3 + app/test-pmd/noisy_vnf.c | 8 +- app/test-pmd/testpmd.c | 44 +++- app/test-pmd/testpmd.h | 25 ++- doc/guides/rel_notes/release_23_03.rst | 8 + doc/guides/testpmd_app_ug/testpmd_funcs.rst | 7 + lib/eal/common/eal_common_lcore.c | 222 ++++++++++++++++++-- lib/eal/include/rte_lcore.h | 48 +++++ lib/eal/version.map | 1 + 9 files changed, 335 insertions(+), 31 deletions(-) -- 2.39.1
