On Fri, 21 Aug 2020 13:12:59 -0600 David Ahern wrote: > On 8/21/20 10:53 AM, Jakub Kicinski wrote: > > How many times do I have to say that I'm not arguing against the value > > of the data? > > > > If you open up this interface either someone will police it, or it will > > become a dumpster. > > I am not following what you are proposing as a solution. You do not like > Ido's idea of stats going through devlink, but you are not being clear > on what you think is a better way. > > You say vxlan stats belong in the vxlan driver, but the stats do not > have to be reported on particular netdevs. How then do h/w stats get > exposed via vxlan code?
No strong preference, for TLS I've done: # cat /proc/net/tls_stat TlsCurrTxSw 0 TlsCurrRxSw 0 TlsCurrTxDevice 0 TlsCurrRxDevice 0 TlsTxSw 0 TlsRxSw 0 TlsTxDevice 0 TlsRxDevice 0 TlsDecryptError 0 TlsRxDeviceResync 0 We can add something over netlink, I opted for simplicity since global stats don't have to scale with number of interfaces.
