diff options
author | 2019-07-30 15:20:41 +0300 | |
---|---|---|
committer | 2019-07-31 19:13:40 -0400 | |
commit | 3247b272048ffefc12c7dcfa3169bd03047a49bc (patch) | |
tree | 0e0d9639b882dbc452c6bc337adc201d54fa6eaf /include/uapi | |
parent | tc-testing: Clarify the use of tdc's -d option (diff) | |
download | linux-3247b272048ffefc12c7dcfa3169bd03047a49bc.tar.gz linux-3247b272048ffefc12c7dcfa3169bd03047a49bc.tar.bz2 linux-3247b272048ffefc12c7dcfa3169bd03047a49bc.zip |
net: bridge: mcast: add delete due to fast-leave mdb flag
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.
Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/uapi')
-rw-r--r-- | include/uapi/linux/if_bridge.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/uapi/linux/if_bridge.h b/include/uapi/linux/if_bridge.h index 773e476a8e54..1b3c2b643a02 100644 --- a/include/uapi/linux/if_bridge.h +++ b/include/uapi/linux/if_bridge.h @@ -237,6 +237,7 @@ struct br_mdb_entry { #define MDB_PERMANENT 1 __u8 state; #define MDB_FLAGS_OFFLOAD (1 << 0) +#define MDB_FLAGS_FAST_LEAVE (1 << 1) __u8 flags; __u16 vid; struct { |