On Mon, 29 Nov 2021 18:08:12 +0100 Petr Machata wrote: > Jakub Kicinski <kuba@xxxxxxxxxx> writes: > > On Mon, 29 Nov 2021 16:51:02 +0100 Petr Machata wrote: > >> IFLA_STATS_LINK_OFFLOAD_XSTATS is a nest. Currently it carries just > >> CPU_HIT stats. The idea is to carry HW stats as well in that group. > > > > Hm, the expectation was that the HW stats == total - SW. I believe that > > still holds true for you, even if HW stats are not "complete" (e.g. > > user enabled them after device was already forwarding for a while). > > Is the concern about backward compat or such? > > I guess you could call it backward compat. But not only. I think a > typical user doing "ip -s l sh", including various scripts, wants to see > the full picture and not worry what's going on where. Physical > netdevices already do that, and by extension bond and team of physical > netdevices. It also makes sense from the point of view of an offloaded > datapath as an implementation detail that you would ideally not notice. Agreed. > For those who care to know about the offloaded datapath, it would be > nice to have the option to request either just the SW stats, or just the > HW stats. A logical place to put these would be under the OFFLOAD_XSTATS > nest of the RTM_GETSTATS message, but maybe the SW ones should be up > there next to IFLA_STATS_LINK_64. (After all it's going to be > independent from not only offload datapath, but also XDP.) What I'm getting at is that I thought IFLA_OFFLOAD_XSTATS_CPU_HIT should be sufficient from uAPI perspective in terms of reporting. User space can do the simple math to calculate the "SW stats" if it wants to. We may well be talking about the same thing, so maybe let's wait for the code? > This way you get the intuitive default behavior, but still have a way to > e.g. request just the SW stats without hitting the HW, or just request > the HW stats if that's what you care about.
