From: Petr Machata <petrm@nvidia•com>
To: Nikolay Aleksandrov <razor@blackwall•org>
Cc: Petr Machata <petrm@nvidia•com>, <netdev@vger•kernel.org>,
<dsahern@gmail•com>, <stephen@networkplumber•org>,
Ido Schimmel <idosch@nvidia•com>
Subject: Re: [PATCH iproute2-next 3/3] man: man8: bridge: Describe mcast_max_groups
Date: Tue, 7 Feb 2023 10:49:32 +0100 [thread overview]
Message-ID: <87sffhdcsm.fsf@nvidia.com> (raw)
In-Reply-To: <0b6635f8-1b5a-80ec-8cc8-5b463d963d2c@blackwall.org>
Nikolay Aleksandrov <razor@blackwall•org> writes:
> On 2/6/23 19:50, Petr Machata wrote:
>> Add documentation for per-port and port-port-vlan option mcast_max_groups.
>> Signed-off-by: Petr Machata <petrm@nvidia•com>
>> ---
>> man/man8/bridge.8 | 22 ++++++++++++++++++++++
>> 1 file changed, 22 insertions(+)
>> diff --git a/man/man8/bridge.8 b/man/man8/bridge.8
>> index f73e538a3536..7075eab283fa 100644
>> --- a/man/man8/bridge.8
>> +++ b/man/man8/bridge.8
>> @@ -47,6 +47,8 @@ bridge \- show / manipulate bridge addresses and devices
>> .BR hwmode " { " vepa " | " veb " } ] [ "
>> .BR bcast_flood " { " on " | " off " } ] [ "
>> .BR mcast_flood " { " on " | " off " } ] [ "
>> +.BR mcast_max_groups
>> +.IR MAX_GROUPS " ] ["
>> .BR mcast_router
>> .IR MULTICAST_ROUTER " ] ["
>> .BR mcast_to_unicast " { " on " | " off " } ] [ "
>> @@ -169,6 +171,8 @@ bridge \- show / manipulate bridge addresses and devices
>> .IR VID " [ "
>> .B state
>> .IR STP_STATE " ] [ "
>> +.B mcast_max_groups
>> +.IR MAX_GROUPS " ] [ "
>> .B mcast_router
>> .IR MULTICAST_ROUTER " ]"
>> @@ -517,6 +521,15 @@ By default this flag is on.
>> Controls whether multicast traffic for which there is no MDB entry will be
>> flooded towards this given port. By default this flag is on.
>> +.TP
>> +.BI mcast_max_groups " MAX_GROUPS "
>> +Sets the maximum number of MDB entries that can be registered for a given
>> +port. Attempts to register more MDB entries at the port than this limit
>> +allows will be rejected, whether they are done through netlink (e.g. the
>> +\fBbridge\fR tool), or IGMP or MLD membership reports. Setting a limit to 0
>> +has the effect of disabling the limit. See also the \fBip link\fR option
>> +\fBmcast_hash_max\fR.
>> +
>
> I'd add that the default is 0 (no limit), otherwise looks good to me.
OK.
next prev parent reply other threads:[~2023-02-07 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 17:50 [PATCH iproute2-next 0/3] bridge: Support mcast_n_groups, mcast_max_groups Petr Machata
2023-02-06 17:50 ` [PATCH iproute2-next 1/3] uapi: Update if_bridge, if_link Petr Machata
2023-02-06 17:50 ` [PATCH iproute2-next 2/3] bridge: Add support for mcast_n_groups, mcast_max_groups Petr Machata
2023-02-07 7:39 ` Ido Schimmel
2023-02-06 17:50 ` [PATCH iproute2-next 3/3] man: man8: bridge: Describe mcast_max_groups Petr Machata
2023-02-06 23:08 ` Nikolay Aleksandrov
2023-02-07 9:49 ` Petr Machata [this message]
2023-02-07 7:50 ` Ido Schimmel
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=87sffhdcsm.fsf@nvidia.com \
--to=petrm@nvidia$(echo .)com \
--cc=dsahern@gmail$(echo .)com \
--cc=idosch@nvidia$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=razor@blackwall$(echo .)org \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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