netdev - Re: [PATCH v4 net-next 00/20] net: Enable nexthop objects with IPv4 and IPv6 routes

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] [day] [month] [year] [list]

Message-Id: <20190610.110655.452387337378630657.davem@davemloft.net>
Date:   Mon, 10 Jun 2019 11:06:55 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     weiwan@...gle.com
Cc:     dsahern@...nel.org, netdev@...r.kernel.org, idosch@...lanox.com,
        kafai@...com, sbrivio@...hat.com, dsahern@...il.com
Subject: Re: [PATCH v4 net-next 00/20] net: Enable nexthop objects with
 IPv4 and IPv6 routes

From: Wei Wang <weiwan@...gle.com>
Date: Sun, 9 Jun 2019 22:11:33 -0700

> On Sat, Jun 8, 2019 at 2:53 PM David Ahern <dsahern@...nel.org> wrote:
>>
>> From: David Ahern <dsahern@...il.com>
>>
>> This is the final set of the initial nexthop object work. When I
>> started this idea almost 2 years ago, it took 18 seconds to inject
>> 700k+ IPv4 routes with 1 hop and about 28 seconds for 4-paths. Some
>> of that time was due to inefficiencies in 'ip', but most of it was
>> kernel side with excessive synchronize_rcu calls in ipv4, and redundant
>> processing validating a nexthop spec (device, gateway, encap). Worse,
>> the time increased dramatically as the number of legs in the routes
>> increased; for example, taking over 72 seconds for 16-path routes.
 ...
> For all ipv6 patches:
> Reviewed-By: Wei Wang <weiwan@...gle.com>

Series applied, thanks.