This patch set adds some features and small fixes in the FDB table manipulation area.
First of all, we implement the .ndo_fdb_dump netdev callback so that all offloaded FDB entries, either static or learnt, are available to the user. This is necessary because the DPAA2 switch does not emit interrupts when a new FDB is learnt or deleted, thus we are not able to keep the software bridge state and the HW in sync by calling the switchdev notifiers. The patch set also adds the .ndo_fdb_[add|del] callbacks in order to facilitate adding FDB entries not associated with any master device. One interesting thing that I observed is that when adding an FDB entry associated with a bridge (ie using the 'master' keywork appended to the bridge command) and then dumping the FDB entries, there will be duplicates of the same entry: one listed by the bridge device and one by the driver's .ndo_fdb_dump). It raises the question whether this is the expected behavior or not. Another concern is regarding the correct/desired machanism for drivers to signal errors back to switchdev on adding or deleting an FDB entry. In the switchdev documentation, there is a TODO in the place of this topic. Ioana Ciornei (5): staging: fsl-dpaa2/ethsw: remove unused structure staging: fsl-dpaa2/ethsw: notify switchdev of offloaded entry staging: fsl-dpaa2/ethsw: add .ndo_fdb_dump callback staging: fsl-dpaa2/ethsw: check added_by_user flag staging: fsl-dpaa2/ethsw: add .ndo_fdb[add|del] callbacks drivers/staging/fsl-dpaa2/ethsw/TODO | 1 - drivers/staging/fsl-dpaa2/ethsw/dpsw-cmd.h | 15 ++- drivers/staging/fsl-dpaa2/ethsw/dpsw.c | 51 +++++++++ drivers/staging/fsl-dpaa2/ethsw/dpsw.h | 56 ++++----- drivers/staging/fsl-dpaa2/ethsw/ethsw.c | 178 ++++++++++++++++++++++++++++- 5 files changed, 265 insertions(+), 36 deletions(-) -- 1.9.1
