linux-toradex.git/include/net/switchdev.h, branch v4.16-rc4

net: bridge: Add/del switchdev object on host join/leave

2017-11-10T04:41:40+00:00

When the host joins or leaves a multicast group, use switchdev to add
an object to the hardware to forward traffic for the group to the
host.

Signed-off-by: Andrew Lunn 
Acked-by: Nikolay Aleksandrov 
Signed-off-by: David S. Miller

net: bridge: Notify on bridge device mrouter state changes

2017-10-09T17:18:11+00:00

Add the SWITCHDEV_ATTR_ID_BRIDGE_MROUTER switchdev notification type, used
to indicate whether the bridge is or isn't mrouter. Notify when the bridge
changes its state, similarly to the already existing bridged port mrouter
notifications.

The notification uses the switchdev_attr.u.mrouter boolean flag to indicate
the current bridge mrouter status. Thus, it only indicates whether the
bridge is currently used as an mrouter or not, and does not indicate the
exact mrouter state of the bridge (learning, permanent, etc.).

Signed-off-by: Yotam Gigi 
Signed-off-by: Jiri Pirko 
Signed-off-by: Nikolay Aleksandrov 
Signed-off-by: David S. Miller

net: switchdev: Remove bridge bypass support from switchdev

2017-08-07T21:48:48+00:00

Currently the bridge port flags, vlans, FDBs and MDBs can be offloaded
through the bridge code, making the switchdev's SELF bridge bypass
implementation to be redundant. This implies several changes:
- No need for dump infra in switchdev, DSA's special case is handled
  privately.
- Remove obj_dump from switchdev_ops.
- FDBs are removed from obj_add/del routines, due to the fact that they
  are offloaded through the bridge notification chain.
- The switchdev_port_bridge_xx() and switchdev_port_fdb_xx() functions
  can be removed.

Signed-off-by: Arkadi Sharshevsky 
Reviewed-by: Vivien Didelot 
Acked-by: Jiri Pirko 
Reviewed-by: Ivan Vecera 
Reviewed-by: Florian Fainelli 
Signed-off-by: David S. Miller

net: dsa: Move FDB dump implementation inside DSA

2017-08-07T21:48:48+00:00

>From all switchdev devices only DSA requires special FDB dump. This is due
to lack of ability for syncing the hardware learned FDBs with the bridge.
Due to this it is removed from switchdev and moved inside DSA.

Signed-off-by: Arkadi Sharshevsky 
Signed-off-by: David S. Miller

net: switchdev: add SET_SWITCHDEV_OPS helper

2017-07-01T15:51:32+00:00

Add a helper to allow switchdev ops to be set if NET_SWITCHDEV is configured
and do nothing otherwise. This allows for slightly cleaner code which
uses switchdev but does not select NET_SWITCHDEV.

Signed-off-by: Simon Horman 
Acked-by: Ivan Vecera 
Signed-off-by: David S. Miller

net: bridge: Receive notification about successful FDB offload

2017-06-08T18:16:25+00:00

When a new static FDB is added to the bridge a notification is sent to
the driver for offload. In case of successful offload the driver should
notify the bridge back, which in turn should mark the FDB as offloaded.

Currently, externally learned is equivalent for being offloaded which is
not correct due to the fact that FDBs which are added from user-space are
also marked as externally learned. In order to specify if an FDB was
successfully offloaded a new flag is introduced.

Signed-off-by: Arkadi Sharshevsky 
Reviewed-by: Ido Schimmel 
Reviewed-by: Nikolay Aleksandrov 
Signed-off-by: Jiri Pirko 
Signed-off-by: David S. Miller

net: bridge: Add support for notifying devices about FDB add/del

2017-06-08T18:16:25+00:00

Currently the bridge doesn't notify the underlying devices about new
FDBs learned. The FDB sync is placed on the switchdev notifier chain
because devices may potentially learn FDB that are not directly related
to their ports, for example:

1. Mixed SW/HW bridge - FDBs that point to the ASICs external devices
                        should be offloaded as CPU traps in order to
			perform forwarding in slow path.
2. EVPN - Externally learned FDBs for the vtep device.

Notification is sent only about static FDB add/del. This is done due
to fact that currently this is the only scenario supported by switch
drivers.

Signed-off-by: Arkadi Sharshevsky 
Reviewed-by: Ido Schimmel 
Signed-off-by: Jiri Pirko 
Reviewed-by: Nikolay Aleksandrov 
Reviewed-by: Ivan Vecera 
Signed-off-by: David S. Miller

net: switchdev: Add support for querying supported bridge flags by hardware

2017-06-08T18:16:23+00:00

This is done as a preparation stage before setting the bridge port flags
from the bridge code. Currently the device can be queried for the bridge
flags state, but the querier cannot distinguish if the flag is disabled
or if it is not supported at all. Thus, add new attr and a bit-mask which
include information regarding the support on a per-flag basis.

Drivers that support bridge offload but not support bridge flags should
return zeroed bitmask.

Signed-off-by: Arkadi Sharshevsky 
Reviewed-by: Ido Schimmel 
Reviewed-by: Ivan Vecera 
Signed-off-by: Jiri Pirko 
Reviewed-by: Ivan Vecera 
Signed-off-by: David S. Miller

switchdev: bridge: Offload mc router ports

2017-02-10T16:46:39+00:00

Offload the mc router ports list, whenever it is being changed.
It is done because in some cases mc packets needs to be flooded to all
the ports in this list.

Signed-off-by: Nogah Frankel 
Signed-off-by: Yotam Gigi 
Signed-off-by: Jiri Pirko 
Acked-by: Ivan Vecera 
Signed-off-by: David S. Miller

switchdev: bridge: Offload multicast disabled

2017-02-10T16:46:38+00:00

Offload multicast disabled flag, for more accurate mc flood behavior:
When it is on, the mdb should be ignored.
When it is off, unregistered mc packets should be flooded to mc router
ports.

Signed-off-by: Nogah Frankel 
Signed-off-by: Yotam Gigi 
Signed-off-by: Jiri Pirko 
Acked-by: Ivan Vecera 
Signed-off-by: David S. Miller