diff options
author | Nikolay Aleksandrov <nikolay@cumulusnetworks.com> | 2019-07-30 14:20:41 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-08-01 01:13:40 +0200 |
commit | 3247b272048ffefc12c7dcfa3169bd03047a49bc (patch) | |
tree | 0e0d9639b882dbc452c6bc337adc201d54fa6eaf /net/bridge/br_mdb.c | |
parent | tc-testing: Clarify the use of tdc's -d option (diff) | |
download | linux-3247b272048ffefc12c7dcfa3169bd03047a49bc.tar.xz 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 'net/bridge/br_mdb.c')
-rw-r--r-- | net/bridge/br_mdb.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/net/bridge/br_mdb.c b/net/bridge/br_mdb.c index bf6acd34234d..428af1abf8cc 100644 --- a/net/bridge/br_mdb.c +++ b/net/bridge/br_mdb.c @@ -60,6 +60,8 @@ static void __mdb_entry_fill_flags(struct br_mdb_entry *e, unsigned char flags) e->flags = 0; if (flags & MDB_PG_FLAGS_OFFLOAD) e->flags |= MDB_FLAGS_OFFLOAD; + if (flags & MDB_PG_FLAGS_FAST_LEAVE) + e->flags |= MDB_FLAGS_FAST_LEAVE; } static void __mdb_entry_to_br_ip(struct br_mdb_entry *entry, struct br_ip *ip) |