06/02/2018 17:06, Bruce Richardson: > When querying either the name or the value of a stat using the xstats > APIs, a check is done to see if the regular stats API or the xstats APIs > for the driver need to be used. However, the id of the stat requested is > checked to see if it is greater than the number of basic stats, rather > than checking for greater-or-equal, meaning that the xstat with the lowest > id gets incorrectly treated as a basic stat. > > This problem manifests itself when you call proc_info using "--xstats-id" > for the first xstat, you get no name of the stat printed, and a random(ish) > stat value. > > Fixes: 4773152f850b ("ethdev: optimize xstats by ids APIs") > > Signed-off-by: Bruce Richardson <bruce.richard...@intel.com>
Applied, thanks It looks like the stats functions are the most reworked and fixed. It is a no-end story. According to git statistics, it is probably the most complicate code of DPDK :) I am thinking about being more conservative and do not accept any new change in these rocket science functions ;)