From: David Miller <davem@davemloft.net>
To: nikolay@cumulusnetworks.com
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
sashok@cumulusnetworks.com, stephen@networkplumber.org,
liuhangbin@gmail.com
Subject: Re: [PATCH net-next 0/2] bridge: add support for IGMPv3 and MLDv2 querier
Date: Mon, 21 Nov 2016 13:17:15 -0500 (EST) [thread overview]
Message-ID: <20161121.131715.1012790937919983633.davem@davemloft.net> (raw)
In-Reply-To: <1479729805-23108-1-git-send-email-nikolay@cumulusnetworks.com>
From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Date: Mon, 21 Nov 2016 13:03:23 +0100
> This patch-set adds support for IGMPv3 and MLDv2 querier in the bridge.
> Two new options which can be toggled via netlink and sysfs are added that
> control the version per-bridge:
> multicast_igmp_version - default 2, can be set to 3
> multicast_mld_version - default 1, can be set to 2 (this option is
> disabled if CONFIG_IPV6=n)
>
> Note that the names do not include "querier", I think that these options
> can be re-used later as more IGMPv3 support is added to the bridge so we
> can avoid adding more options to switch between v2 and v3 behaviour.
>
> The set uses the already existing br_ip{4,6}_multicast_alloc_query
> functions and adds the appropriate header based on the chosen version.
>
> For the initial support I have removed the compatibility implementation
> (RFC3376 sec 7.3.1, 7.3.2; RFC3810 sec 8.3.1, 8.3.2), because there are
> some details that we need to sort out.
Series applied, thanks.
prev parent reply other threads:[~2016-11-21 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 12:03 [PATCH net-next 0/2] bridge: add support for IGMPv3 and MLDv2 querier Nikolay Aleksandrov
2016-11-21 12:03 ` [PATCH net-next 1/2] bridge: mcast: add IGMPv3 query support Nikolay Aleksandrov
2016-11-21 12:03 ` [PATCH net-next 2/2] bridge: mcast: add MLDv2 querier support Nikolay Aleksandrov
2016-11-21 18:17 ` David Miller [this message]
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=20161121.131715.1012790937919983633.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=sashok@cumulusnetworks.com \
--cc=stephen@networkplumber.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).