netdev - Re: [PATCH net-next 0/5] mlxsw: Update adjacency index more efficiently

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4c97e61a-6267-f4c1-5e82-f8b3f15252e7@gmail.com>
Date:   Wed, 25 Nov 2020 15:53:57 -0700
From:   David Ahern <dsahern@...il.com>
To:     Ido Schimmel <idosch@...sch.org>, netdev@...r.kernel.org
Cc:     davem@...emloft.net, kuba@...nel.org, jiri@...dia.com,
        mlxsw@...dia.com, Ido Schimmel <idosch@...dia.com>
Subject: Re: [PATCH net-next 0/5] mlxsw: Update adjacency index more
 efficiently

On 11/25/20 12:35 PM, Ido Schimmel wrote:
> Example:
> 
> 8k IPv6 routes were added in an alternating manner to two VRFs. All the
> routes are using the same nexthop object ('nhid 1').
> 
> Before:
> 
> # perf stat -e devlink:devlink_hwmsg --filter='incoming==0' -- ip nexthop replace id 1 via 2001:db8:1::2 dev swp3
> 
>  Performance counter stats for 'ip nexthop replace id 1 via 2001:db8:1::2 dev swp3':
> 
>             16,385      devlink:devlink_hwmsg
> 
>        4.255933213 seconds time elapsed
> 
>        0.000000000 seconds user
>        0.666923000 seconds sys
> 
> Number of EMAD transactions corresponds to number of routes using the
> nexthop group.
> 
> After:
> 
> # perf stat -e devlink:devlink_hwmsg --filter='incoming==0' -- ip nexthop replace id 1 via 2001:db8:1::2 dev swp3
> 
>  Performance counter stats for 'ip nexthop replace id 1 via 2001:db8:1::2 dev swp3':
> 
>                  3      devlink:devlink_hwmsg
> 
>        0.077655094 seconds time elapsed
> 
>        0.000000000 seconds user
>        0.076698000 seconds sys
> 
> Number of EMAD transactions corresponds to number of VRFs / VRs.

wow, that is a huge difference - a good example of the efficiencies the
nexthop model allows.