netdev - Re: [PATCH net-next] ipv6: Move ipv6 stubs to a separate header file

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, 25 Mar 2019 20:22:33 -0600
From:   David Ahern <dsahern@...il.com>
To:     Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc:     David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
        edumazet@...gle.com
Subject: Re: [PATCH net-next] ipv6: Move ipv6 stubs to a separate header file

On 3/24/19 9:26 PM, Alexei Starovoitov wrote:
> The kernel has to be fast as a dataplane but these extra features
> will slow down the routing by making kernel-as-database scale a bit better.

I took Vincent Bernat's fib lookup microbenchmark and added input and
output route lookups to it. Through this commit:

commit 4d5edf447c88e59f5c5716180c1001cde9bf4473
Author: David Ahern <dsahern@...il.com>
Date:   Mon Mar 11 18:34:48 2019 -0700

    ipv4: Allow ipv6 gateway with ipv4 routes

There is no real measurable difference for IPv4 fib lookups
(fib_lookup), input routes (ip_route_input_rcu) and output routes
(ip_route_output_key_hash_rcu). This is using a bare metal server with a
L5640 Xeon CPU.

The above commit is the target for the first 2 rounds of patches. I will
of course be checking performance each step along the way to nexthop
objects.