All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsa@cumulusnetworks.com>
To: Vincent Bernat <vincent@bernat.im>,
	"David S. Miller" <davem@davemloft.net>,
	Nicolas Dichtel <nicolas.dichtel@6wind.com>,
	Wilson Kok <wkok@cumulusnetworks.com>,
	netdev@vger.kernel.org
Subject: Re: [net v1] fib_rules: interface group matching
Date: Wed, 14 Sep 2016 08:15:21 -0600	[thread overview]
Message-ID: <9540c014-78c5-9f9c-16d7-75a564f6c018@cumulusnetworks.com> (raw)
In-Reply-To: <20160914124025.13417-1-vincent@bernat.im>

On 9/14/16 6:40 AM, Vincent Bernat wrote:
> When a user wants to assign a routing table to a group of incoming
> interfaces, the current solutions are:
> 
>  - one IP rule for each interface (scalability problems)
>  - use of fwmark and devgroup matcher (don't work with internal route
>    lookups, used for example by RPF)
>  - use of VRF devices (more complex)

Why do you believe that? A VRF is a formalized grouping of interfaces that includes an API for locally generated traffic to specify which VRF/group to use. And, with the l3mdev rule you only need 1 rule for all VRFs regardless of the number which is the best solution to the scalability problem of adding rules per device/group/VRF.

What use case are trying to solve?

  parent reply	other threads:[~2016-09-14 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 12:40 [net v1] fib_rules: interface group matching Vincent Bernat
2016-09-14 12:43 ` Vincent Bernat
2016-09-14 14:15 ` David Ahern [this message]
2016-09-14 14:25   ` Vincent Bernat
2016-09-14 14:39     ` David Ahern
2016-09-14 15:14       ` Vincent Bernat
2016-09-14 15:25         ` David Ahern
2016-09-14 16:01           ` Vincent Bernat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9540c014-78c5-9f9c-16d7-75a564f6c018@cumulusnetworks.com \
    --to=dsa@cumulusnetworks.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=vincent@bernat.im \
    --cc=wkok@cumulusnetworks.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.