From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: netdev@vger.kernel.org, idosch@mellanox.com, mlxsw@mellanox.com,
dsa@cumulusnetworks.com, shm@cumulusnetworks.com,
kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net, lorenzo@google.com, mateusz.bajorski@nokia.com
Subject: Re: [patch net-next v3 0/9] mlxsw: Enable VRF offload
Date: Thu, 16 Mar 2017 10:20:22 -0700 (PDT) [thread overview]
Message-ID: <20170316.102022.1371204829896380177.davem@davemloft.net> (raw)
In-Reply-To: <1489651700-3586-1-git-send-email-jiri@resnulli.us>
From: Jiri Pirko <jiri@resnulli.us>
Date: Thu, 16 Mar 2017 09:08:11 +0100
> Packets received from netdevs enslaved to different VRF devices are
> forwarded using different FIB tables. In the Spectrum ASIC this is
> achieved by binding different router interfaces (RIFs) to different
> virtual routers (VRs). Each RIF represents an enslaved netdev and each
> VR has its own FIB table according to which packets are forwarded.
>
> The first three patches add an helper to check if a FIB rule is a
> default rule and extend the FIB notification chain to include the rule's
> info as part of the RULE_{ADD,DEL} events. This allows offloading
> drivers to sanitize the rules they don't support and flush their tables.
>
> The fourth patch introduces a small change in the VRF driver to allow
> capable drivers to more easily offload VRFs.
>
> Finally, the last patches gradually add support for VRFs in the mlxsw
> driver. First, on top of port netdevs, stacked LAG and VLAN devices and
> then on top of bridges.
Series applied, thanks.
prev parent reply other threads:[~2017-03-16 17:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 8:08 [patch net-next v3 0/9] mlxsw: Enable VRF offload Jiri Pirko
2017-03-16 8:08 ` [patch net-next v3 1/9] ipv4: fib_rules: Check if rule is a default rule Jiri Pirko
2017-03-16 15:18 ` David Ahern
2017-03-16 8:08 ` [patch net-next v3 2/9] ipv4: fib_rules: Add notifier info to FIB rules notifications Jiri Pirko
2017-03-16 8:08 ` [patch net-next v3 3/9] ipv4: fib_rules: Dump FIB rules when registering FIB notifier Jiri Pirko
2017-03-16 15:18 ` David Ahern
2017-03-16 8:08 ` [patch net-next v3 4/9] net: vrf: Set slave's private flag before linking Jiri Pirko
2017-03-16 8:08 ` [patch net-next v3 5/9] mlxsw: spectrum_router: Associate RIFs with correct VR Jiri Pirko
2017-03-16 8:08 ` [patch net-next v3 6/9] mlxsw: spectrum_router: Don't destroy RIF if L3 slave Jiri Pirko
2017-03-16 8:08 ` [patch net-next v3 7/9] mlxsw: spectrum_router: Add support for VRFs Jiri Pirko
2017-03-16 8:08 ` [patch net-next v3 8/9] mlxsw: spectrum_router: Add support for VRFs on top of bridges Jiri Pirko
2017-03-16 8:08 ` [patch net-next v3 9/9] mlxsw: spectrum_router: Don't abort on l3mdev rules Jiri Pirko
2017-03-16 17:20 ` David Miller [this message]
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=20170316.102022.1371204829896380177.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=lorenzo@google.com \
--cc=mateusz.bajorski@nokia.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=shm@cumulusnetworks.com \
--cc=yoshfuji@linux-ipv6.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).