From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: netdev@vger.kernel.org
Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
roopa@cumulusnetworks.com, bridge@lists.linux-foundation.org,
davem@davemloft.net
Subject: [PATCH net-next 0/3] bridge: mcast: add support for temp router port
Date: Fri, 26 Feb 2016 19:59:23 +0100 [thread overview]
Message-ID: <1456513166-20159-1-git-send-email-nikolay@cumulusnetworks.com> (raw)
Hi,
This set adds support for temporary router port which doesn't depend on
the incoming queries. It can be refreshed by setting multicast_router to
the same value (3). The first two patches are minor changes that prepare
the code for the third which adds this new type of router port.
In order to be able to dump its information the mdb router port format
is changed and extended similar to how mdb entries format was done
recently.
The related iproute2 changes will be posted if this is accepted.
Thanks,
Nik
Nikolay Aleksandrov (3):
bridge: mcast: use names for the different multicast_router types
bridge: mcast: do nothing if port's multicast_router is set to the
same val
bridge: mcast: add support for temporary port router
include/uapi/linux/if_bridge.h | 22 +++++++++++-
net/bridge/br_mdb.c | 16 +++++++--
net/bridge/br_multicast.c | 80 +++++++++++++++++++++++++++---------------
3 files changed, 86 insertions(+), 32 deletions(-)
--
2.4.3
next reply other threads:[~2016-02-26 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 18:59 Nikolay Aleksandrov [this message]
2016-02-26 18:59 ` [PATCH net-next 1/3] bridge: mcast: use names for the different multicast_router types Nikolay Aleksandrov
2016-02-26 18:59 ` [PATCH net-next 2/3] bridge: mcast: do nothing if port's multicast_router is set to the same val Nikolay Aleksandrov
2016-02-26 18:59 ` [PATCH net-next 3/3] bridge: mcast: add support for temporary port router Nikolay Aleksandrov
2016-02-26 19:51 ` [PATCH net-next 0/3] bridge: mcast: add support for temp router port 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=1456513166-20159-1-git-send-email-nikolay@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
/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).