netdev - Re: [PATCH net-next 0/2] net: introduce and use route hint

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 18 Nov 2019 09:12:53 +0100
From:   Paolo Abeni <pabeni@...hat.com>
To:     David Miller <davem@...emloft.net>
Cc:     netdev@...r.kernel.org, willemdebruijn.kernel@...il.com,
        ecree@...arflare.com
Subject: Re: [PATCH net-next 0/2] net: introduce and use route hint

On Sat, 2019-11-16 at 12:09 -0800, David Miller wrote:
> From: Paolo Abeni <pabeni@...hat.com>
> Date: Sat, 16 Nov 2019 10:14:49 +0100
> 
> > This series leverages the listification infrastructure to avoid
> > unnecessary route lookup on ingress packets. In absence of policy routing,
> > packets with equal daddr will usually land on the same dst.
> > 
> > When processing packet bursts (lists) we can easily reference the previous
> > dst entry. When we hit the 'same destination' condition we can avoid the
> > route lookup, coping the already available dst.
> > 
> > Detailed performance numbers are available in the individual commit messages.
> 
> Looks like there are some problems with the unconditional use of
> fib{6}_has_custom_rules in this series.

Whoops... I forgot the dependency on CONFIG_IP*_MULTIPLE_TABLES. I'll
fix that in the next iteration.

Thanks,

Paolo