- 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: -
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:
-
