[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170316.102022.1371204829896380177.davem@davemloft.net>
Date: Thu, 16 Mar 2017 10:20:22 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jiri@...nulli.us
Cc: netdev@...r.kernel.org, idosch@...lanox.com, mlxsw@...lanox.com,
dsa@...ulusnetworks.com, shm@...ulusnetworks.com,
kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org,
kaber@...sh.net, lorenzo@...gle.com, mateusz.bajorski@...ia.com
Subject: Re: [patch net-next v3 0/9] mlxsw: Enable VRF offload
From: Jiri Pirko <jiri@...nulli.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.
Powered by blists - more mailing lists