> From: fengchengwen [mailto:fengcheng...@huawei.com] > Sent: Monday, 6 February 2023 05.00 > > Hi Robin, > > On 2023/2/2 21:43, Robin Jarry wrote: > > Allow applications to register a callback that will be invoked in > > rte_lcore_dump() and when requesting lcore info in the telemetry API. > > > > The callback is expected to return the number of TSC cycles that have > > passed since application start and the number of these cycles that > were > > spent doing busy work. > > > > The 'record_burst_stats' also important for performance tune.
While I agree that burst size spread is important for comparing CPU usage and capacity, the 'record_burst_stats' is a test_pmd specific feature. Applications may implement something different. > > Is it possible to incorporate it into this framework? We all agreed on CPU usage metrics for this patch, so let's limit ourselves this time. If we want more performance metrics, such as RX and TX burst size spread, they can be proposed and discussed in a separate RFC. It might trigger a lot of discussion, like the original lcore busyness patch that inspired this patch series.