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: Mon, 5 Mar 2018 16:16:13 -0800 From: Jakub Kicinski <jakub.kicinski@...ronome.com> To: John Hurley <john.hurley@...ronome.com> Cc: Or Gerlitz <gerlitz.or@...il.com>, Linux Netdev List <netdev@...r.kernel.org>, Jiri Pirko <jiri@...lanox.com>, Or Gerlitz <ogerlitz@...lanox.com>, Simon Horman <simon.horman@...ronome.com> Subject: Re: [RFC net-next 0/6] offload linux bonding tc ingress rules On Mon, 5 Mar 2018 23:57:18 +0000, John Hurley wrote: > > what is your approach for rules whose bond is their egress device > > (ingress = vf port > > representor)? > > Egress offload will be handled entirely by the NFP driver. > Basically, notifiers will track the slaves/masters and update the card > with any groups that consist entirely of reprs. > We then offload the TC rule outputting to the given group - because it > is an ingress match we can access the egress netdev in the block > callback. And you handle egdev call too? Or are we hoping to get rid of that before? :)
Powered by blists - more mailing lists