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, 10 Nov 2016 10:10:25 -0800 From: Pravin Shelar <pshelar@....org> To: Jiri Benc <jbenc@...hat.com> Cc: Linux Kernel Network Developers <netdev@...r.kernel.org> Subject: Re: [PATCH net-next v2 4/7] vxlan: improve vxlan route lookup checks. On Thu, Nov 10, 2016 at 1:56 AM, Jiri Benc <jbenc@...hat.com> wrote: > On Wed, 9 Nov 2016 19:34:06 -0800, Pravin Shelar wrote: >> Why it would not help in non-ovs vxlan egress path? It avoids checking >> (if condition) for device loop. > > I may be missing something but I count the same number of conditions > for each packet, they're just at a different place after the patch. > I am specifically talking about cached routes. If the dst entry is cached, this patch avoids checking for device loop. > E.g. for IPv4, the "if (!sock4)" is moved from vxlan_xmit_one into > vxlan_get_route and the "rt" error handling stays logically the same > (three if conditions in the non-error path) but is moved into > vxlan_get_route. Similarly for IPv6. > > Jiri
Powered by blists - more mailing lists