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
| ||
|
Date: Sat, 13 Jul 2019 19:38:51 -0700 (PDT) From: David Miller <davem@...emloft.net> To: idosch@...sch.org Cc: nhorman@...driver.com, netdev@...r.kernel.org, jiri@...lanox.com, mlxsw@...lanox.com, dsahern@...il.com, roopa@...ulusnetworks.com, nikolay@...ulusnetworks.com, andy@...yhouse.net, pablo@...filter.org, jakub.kicinski@...ronome.com, pieter.jansenvanvuuren@...ronome.com, andrew@...n.ch, f.fainelli@...il.com, vivien.didelot@...il.com, idosch@...lanox.com Subject: Re: [PATCH net-next 00/11] Add drop monitor for offloaded data paths From: Ido Schimmel <idosch@...sch.org> Date: Thu, 11 Jul 2019 15:39:09 +0300 > Before I start working on v2, I would like to get your feedback on the > high level plan. Also adding Neil who is the maintainer of drop_monitor > (and counterpart DropWatch tool [1]). > > IIUC, the problem you point out is that users need to use different > tools to monitor packet drops based on where these drops occur > (SW/HW/XDP). > > Therefore, my plan is to extend the existing drop_monitor netlink > channel to also cover HW drops. I will add a new message type and a new > multicast group for HW drops and encode in the message what is currently > encoded in the devlink events. Consolidating the reporting to merge with the drop monitor facilities is definitely a step in the right direction.
Powered by blists - more mailing lists