Mon, Jun 20, 2016 at 02:28:31PM CEST, j...@mojatatu.com wrote: >On 16-06-19 11:14 PM, Roopa Prabhu wrote: >>On Fri, Jun 17, 2016 at 10:12 AM, Florian Fainelli <f.faine...@gmail.com> >>wrote: > > >> >>I have also mentioned this before, the default api must provide >>accumulated (hw and sw) stats..., >>because this is the api that the user queries on an interface. > >Sorry - I missed those discussions. >What is current practise? Do people request for one via ip link >stats and the other via ethtool?
Yes. >What do you guys do in your implementation? Currently we do what you described. This patchset changes it. >Yes, it would be more accurate to provide aggregated stats but >it may break backward compat if expectation is both are read >separately today. >Maybe it makes sense to have a brand new TLV for these aggregated >stats as Jiri was suggesting.That means two new TLVs not one. >1) TLV for aggregated stats - which cant be current one >2) TLV for h/w stats > >The existing stat implies s/ware only. What is "aggregated"? if hw counts it, sw counts it as well. HW stats are in fact aggregated. It includes all. Apps should see HW stats as they don't care if the forwarding is offloaded to HW or not. And if someone is aware there is a forward offload, he can query sw-only stats via iface proposed by this patchset.
