From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH RFC net-next 1/4] ipv4: fib_rules: support match on
 sport, dport and ip proto
Date: Mon, 12 Feb 2018 19:03:28 -0500 (EST)
Message-ID: <20180212.190328.237718184085028920.davem@davemloft.net>
References: <1518468573.3715.163.camel@gmail.com>
        <20180212.160510.620630476824737121.davem@davemloft.net>
        <1518472499.3715.165.camel@gmail.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: roopa@cumulusnetworks.com, netdev@vger.kernel.org,
        dsa@cumulusnetworks.com, nikolay@cumulusnetworks.com
To: eric.dumazet@gmail.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([184.105.139.130]:60178 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932641AbeBMADc (ORCPT
        <rfc822;netdev@vger.kernel.org>); Mon, 12 Feb 2018 19:03:32 -0500
In-Reply-To: <1518472499.3715.165.camel@gmail.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Mon, 12 Feb 2018 13:54:59 -0800

> We had project/teams using different routing tables for each vlan they
> setup :/

Indeed, people use FIB rules and think they can scale in software.  As
currently implemented, they can't.

The example you give sounds possibly like a great VRF use case btw :-)