Thread (5 messages) flat view 5 messages, 2 authors, 2016-06-06

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

From: David Miller <davem@davemloft.net>
Date: 2016-06-06 22:47:40

From: David Ahern <redacted>
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help