netdev - Re: [PATCH net-next v3 0/2] net: vrf: Improve use of FIB rules

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, 06 Jun 2016 15:47:38 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dsa@...ulusnetworks.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3 0/2] net: vrf: Improve use of FIB rules

From: David Ahern <dsa@...ulusnetworks.com>
Date: Fri,  3 Jun 2016 12:36:54 -0700

> Currently, VRFs require 1 oif and 1 iif rule per address family per
> VRF. As the number of VRF devices increases it brings scalability
> issues with the increasing rule list. All of the VRF rules have the
> same format with the exception of the specific table id to direct the
> lookup. Since the table id is available from the oif or iif in the
> loopup, the VRF rules can be consolidated to a single rule that pulls
> the table from the VRF device.
> 
> This solution still allows a user to insert their own rules for VRFs,
> including rules with additional attributes. Accordingly, it is backwards
> compatible with existing setups and allows other policy routing as
> desired.

I hate module parameters.

And you don't even need one in this situation, just use a default preference
of 1000 and add a newlink netlink attribute that can change it.

Thanks.