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 linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 21 Aug 2019 20:23:59 -0700 (PDT) From: David Miller <davem@...emloft.net> To: saeedm@...lanox.com Cc: netdev@...r.kernel.org Subject: Re: [pull request][net-next 00/11] Mellanox, mlx5 tc flow handling for concurrent execution (Part 3/3) From: Saeed Mahameed <saeedm@...lanox.com> Date: Wed, 21 Aug 2019 23:28:31 +0000 > This series, mostly from Vlad, is the 3rd and last part of 3 part series > to improve mlx5 tc flow handling by removing dependency on rtnl_lock and > providing a more fine-grained locking and rcu safe data structures to > allow tc flow handling for concurrent execution. > > 2) In this part Vlad handles mlx5e neigh offloads for concurrent > execution. > > 2) Vlad with Dmytro's help, They add 3 new mlx5 tracepoints to track mlx5 > tc flower requests and neigh updates. > > 3) Added mlx5 documentation for the new tracepoints. > > For more information please see tag log below. > > Please pull and let me know if there is any problem. I reviewed this a few times, looks good. Pulled, thanks.
Powered by blists - more mailing lists