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: Thu, 25 Oct 2018 14:52:41 +0200 From: Jiri Pirko <jiri@...nulli.us> To: John Hurley <john.hurley@...ronome.com> Cc: netdev@...r.kernel.org, oss-drivers@...ronome.com, gerlitz.or@...il.com, ozsh@...lanox.com, jakub.kicinski@...ronome.com, simon.horman@...ronome.com, avivh@...lanox.com Subject: Re: [RFC net-next v2 0/8] indirect tc block cb registration Thu, Oct 25, 2018 at 02:26:49PM CEST, john.hurley@...ronome.com wrote: >This patchset introduces an alternative to egdev offload by allowing a >driver to register for block updates when an external device (e.g. tunnel >netdev) is bound to a TC block. Drivers can track new netdevs or register >to existing ones to receive information on such events. Based on this, >they may register for block offload rules using already existing >functions. > >The patchset also implements this new indirect block registration in the >NFP driver to allow the offloading of tunnel rules. The use of egdev >offload (which is currently only used for tunnel offload) is subsequently >removed. John, I'm missing v1->v2 changelog. Could you please add it? Thanks!
Powered by blists - more mailing lists