lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 21 Aug 2020 13:12:59 -0600
From:   David Ahern <dsahern@...il.com>
To:     Jakub Kicinski <kuba@...nel.org>, Ido Schimmel <idosch@...sch.org>
Cc:     Florian Fainelli <f.fainelli@...il.com>, netdev@...r.kernel.org,
        davem@...emloft.net, jiri@...dia.com, amcohen@...dia.com,
        danieller@...dia.com, mlxsw@...dia.com, roopa@...dia.com,
        andrew@...n.ch, vivien.didelot@...il.com, tariqt@...dia.com,
        ayal@...dia.com, mkubecek@...e.cz, Ido Schimmel <idosch@...dia.com>
Subject: Re: [RFC PATCH net-next 0/6] devlink: Add device metric support

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?

Powered by blists - more mailing lists