netdev - Re: [PATCH v2 net-next] ipv6: Implement limits on Hop-by-Hop and Destination options

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]

Message-Id: <20171031.111026.1763034451245817288.davem@davemloft.net>
Date:   Tue, 31 Oct 2017 11:10:26 +0900 (KST)
From:   David Miller <davem@...emloft.net>
To:     tom@...ntonium.net
Cc:     netdev@...r.kernel.org, rohit@...ntonium.net
Subject: Re: [PATCH v2 net-next] ipv6: Implement limits on Hop-by-Hop and
 Destination options

From: Tom Herbert <tom@...ntonium.net>
Date: Mon, 30 Oct 2017 14:16:00 -0700

> I wrote a quick test program that floods a whole bunch of these
> packets to a host and sure enough there is substantial time spent
> in ip6_parse_tlv.
 ...
>   25.38%  [kernel]                    [k] __fib6_clean_all
>   21.63%  [kernel]                    [k] ip6_parse_tlv

Yet the routing code still dominates the cost.