From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: netdev@vger.kernel.org
Cc: herbert@gondor.apana.org.au,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
bridge@lists.linux-foundation.org, davem@davemloft.net
Subject: [PATCH net-next 0/2] bridge: multicast: temp and perm entries behaviour enhancements
Date: Wed, 15 Jul 2015 07:16:49 -0700 [thread overview]
Message-ID: <1436969811-13237-1-git-send-email-nikolay@cumulusnetworks.com> (raw)
Hi,
Patch 01 adds a notify when a group is deleted via br_multicast_del_pg()
(on expire, on device delete or on device down).
Patch 02 changes how bridge device and bridge port delete and down/up are
handled. Until now on bridge down all groups were flushed, now only the
temp ones are (same for port), perm entries are flushed only on port or
bridge removal.
Best regards,
Nikolay Aleksandrov
Nikolay Aleksandrov (2):
bridge: multicast: notify on group delete
bridge: multicast: fix handling of temp and perm entries
net/bridge/br_if.c | 1 +
net/bridge/br_multicast.c | 29 ++++++++++++++++++++++-------
net/bridge/br_private.h | 1 +
3 files changed, 24 insertions(+), 7 deletions(-)
--
1.9.3
next reply other threads:[~2015-07-15 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 14:16 Nikolay Aleksandrov [this message]
2015-07-15 14:16 ` [PATCH net-next 1/2] bridge: multicast: notify on group delete Nikolay Aleksandrov
2015-07-15 14:16 ` [PATCH net-next 2/2] bridge: multicast: fix handling of temp and perm entries Nikolay Aleksandrov
2015-07-20 19:49 ` [PATCH net-next 0/2] bridge: multicast: temp and perm entries behaviour enhancements David Miller
2015-07-20 20:35 ` Nikolay Aleksandrov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1436969811-13237-1-git-send-email-nikolay@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).