- 21 Sep, 2017 40 commits
-
-
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by:Allen Pais <allen.lkml@gmail.com> Signed-off-by:
David S. Miller <davem@davemloft.net>
-
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
Allen Pais authored
Use setup_timer function instead of initializing timer with the function and data fields. Signed-off-by: -
David S. Miller authored
Jiri Pirko says: ==================== mlxsw: Multicast flood update Nogah says: Currently, there are four erroneous flows in MC flood: 1. When MC is disabled it affects only the flood table for unregistered MC packets, but packets that match an entry in the MDB are unaffected. 2. When MC is disabled, MC packets are being sent to all the ports in the bridge (like BC and link-local MC packets) regardless of the designated flag (BR_MCAST_FLAG). 3. When a port is being deleted from a bridge it might remain in the MDB. 4. When MC is enabled packets are flooded to the mrouter ports only if they don't match any entry in the MDB, when they should always be flooded to them. What these problems have in common is the discrepancy between how the hardware handles MDB and mcast flood, and how the driver does it. Each of these problems needs fixing either in the MDB code, or in mcast flood code, and some in both. Patches 1-6 change the way the MDB is handled in the driver to make the following changes easier. Patches 7-8 fix problem number 1 by removing the MDB from the HW when MC is being disabled and restoring it when it is being enabled. Patches 9-10 fix problem number 2 by offloading the flood table by the appropriate flag. Patch 11 fixes problem number 3 by adding MDB flush to the port removal. Patches 12-14 fix problem number 4 by adding the mrouter ports to every MDB entry in the HW to mimic the wanted behaviour. ==================== Signed-off-by: -
Nogah Frankel authored
When a mrouter is registered or leaves a mid, don't update the HW. Signed-off-by:
Nogah Frankel <nogahf@mellanox.com> Signed-off-by:
Jiri Pirko <jiri@mellanox.com> Signed-off-by:
-
Nogah Frankel authored
In mdb flush the port is being removed from all the mids it is registered to. But if the port is mrouter, all the mids floods to it. This patch remove mrouter ports from mids it is not registered to in the mdb flush. Signed-off-by:
-
Nogah Frankel authored
Whenever a port starts / stops being mrouter, update all the mdb entries in the HW to flood / stop flooding mc packets there. The change should happen only if the port is not in the mid. (If it is, the mid should flood mc packets to this port anyway) Signed-off-by:
-
Nogah Frankel authored
When mc is enabled, whenever a mc packet doesn't hit any mdb entry it is being flood to the ports marked as mrouters. However, all mc packets should be flooded to them even if they match an entry in the mdb. This patch adds the mrouter ports to every mdb entry that is being written to the HW. Signed-off-by:
-
Nogah Frankel authored
When a port is being removed from a bridge, flush the bridge mdb to remove the mids of that port. Signed-off-by:
-
Nogah Frankel authored
When multicast is disabled, flood mc packets only to port that are marked BR_MCAST_FLOOD (instead to all). Signed-off-by:
-
Nogah Frankel authored
Use the generic mc flood function to decide whether to flood mc to a port when mc is being enabled / disabled. Move this function in the file to avoid forward declaration. Signed-off-by:
-
Nogah Frankel authored
Remove all the mdb entries from the HW when mc is being disabled and re-write them when it is being enabled. Signed-off-by:
-
Nogah Frankel authored
Don't write multicast related data to the HW when mc is disabled. Also, don't allocate mid id to new mids (so the remove function could know that they weren't wrote to the HW) Signed-off-by:
-
Nogah Frankel authored
Break mid deletion into two function, so it will be possible in the future to delete a mid entry for other reasons then switchdev command (like port deletion). Signed-off-by:
-
Nogah Frankel authored
Attach mid getting and releasing mid id to the HW write / remove, and add a flag to indicate whether the mid is in the HW. It is done because mid id is also HW index to this mid. This change allows adding in the following patches the ability to have a mid in the mdb cache but not in the HW. It will be useful for being able to disable the multicast. It means that the mdb is being written / delete to the HW in the mid allocation / removing function, not after them. Signed-off-by:
-
Nogah Frankel authored
Break the smid write function into two, one that cleans the ports that might be still written there and one that changes an exiting mid entry. Signed-off-by:
-
