In user-space there's no way to distinguish why an mdb entry was deleted and that is a problem for daemons which would like to keep the mdb in sync with remote ends (e.g. mlag) but would also like to converge faster. In almost all cases we'd like to age-out the remote entry for performance and convergence reasons except when fast-leave is enabled. In that case we want explicit immediate remote delete, thus add mdb flag which is set only when the entry is being deleted due to fast-leave.
Showing the changes to include/uapi/linux (1 of 4 files). Show all
Unified · Split
| @@ -237,6 +237,7 @@ struct br_mdb_entry { · 236 unmodified lines | |||
| 237 | #define MDB_PERMANENT 1 | 237 | #define MDB_PERMANENT 1 |
| 238 | __u8 state; | 238 | __u8 state; |
| 239 | #define MDB_FLAGS_OFFLOAD (1 << 0) | 239 | #define MDB_FLAGS_OFFLOAD (1 << 0) |
| 240 | #define MDB_FLAGS_FAST_LEAVE (1 << 1) | ||
| 240 | __u8 flags; | 241 | __u8 flags; |
| 241 | __u16 vid; | 242 | __u16 vid; |
| 242 | struct { | 243 | struct { |