netdev - Re: [PATCH RFC net-next 1/4] ipv4: fib_rules: support match on sport, dport and ip proto

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, 12 Feb 2018 16:03:38 -0700
From:   David Ahern <dsa@...ulusnetworks.com>
To:     Eric Dumazet <eric.dumazet@...il.com>,
        David Miller <davem@...emloft.net>
Cc:     roopa@...ulusnetworks.com, netdev@...r.kernel.org,
        nikolay@...ulusnetworks.com
Subject: Re: [PATCH RFC net-next 1/4] ipv4: fib_rules: support match on sport,
 dport and ip proto

On 2/12/18 2:54 PM, Eric Dumazet wrote:
> On Mon, 2018-02-12 at 16:05 -0500, David Miller wrote:
>> From: Eric Dumazet <eric.dumazet@...il.com>
>> Date: Mon, 12 Feb 2018 12:49:33 -0800
>>
>>> Any setup with about 20 rules to be evaluated (per packet cost) will
>>> feel the pain...
>>>
>>> I wonder if we could JIT/eBPF this thing.
>>
>> That's true for the software implementation angle.
>>
>> But I bet anyone actually using this thing will get it hardware
>> offloaded.
> 
> I wish :)
> 
> We had project/teams using different routing tables for each vlan they
> setup :/

VRF per VLAN, only 1 rule needed

> 
> Setups with tunnels are doubly impacted, it is really easy to reach 20
> evaluated rules per incoming and outgoing packet.
> 
>