From: Stephen Hemminger <stephen@networkplumber.org>
To: Joachim Wiberg <troglobit@gmail.com>
Cc: netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>,
Nikolay Aleksandrov <razor@blackwall.org>
Subject: Re: [PATCH iproute2-next v2 4/6] man: ip-link: document new bcast_flood flag on bridge ports
Date: Tue, 8 Mar 2022 23:28:12 -0800 [thread overview]
Message-ID: <20220308232812.5dc9e7f5@hermes.local> (raw)
In-Reply-To: <20220309071716.2678952-5-troglobit@gmail.com>
On Wed, 9 Mar 2022 08:17:14 +0100
Joachim Wiberg <troglobit@gmail.com> wrote:
> Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
> ---
> man/man8/ip-link.8.in | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/man/man8/ip-link.8.in b/man/man8/ip-link.8.in
> index 19a0c9ca..6dd18f7b 100644
> --- a/man/man8/ip-link.8.in
> +++ b/man/man8/ip-link.8.in
> @@ -2366,6 +2366,8 @@ the following additional arguments are supported:
> ] [
> .BR mcast_flood " { " on " | " off " }"
> ] [
> +.BR bcast_flood " { " on " | " off " }"
> +] [
> .BR mcast_to_unicast " { " on " | " off " }"
> ] [
> .BR group_fwd_mask " MASK"
> @@ -2454,6 +2456,10 @@ option above.
> - controls whether a given port will flood multicast traffic for which
> there is no MDB entry.
>
> +.BR bcast_flood " { " on " | " off " }"
> +- controls flooding of broadcast traffic on the given port. By default
> +this flag is on.
> +
> .BR mcast_to_unicast " { " on " | " off " }"
> - controls whether a given port will replicate packets using unicast
> instead of multicast. By default this flag is off.
Minor nit, would be better to put options in alphabetical order in document.
Certainly not splitting the two mcast options.
next prev parent reply other threads:[~2022-03-09 7:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 7:17 [PATCH iproute2-next v2 0/6] bridge: support for controlling broadcast flooding per port Joachim Wiberg
2022-03-09 7:17 ` [PATCH iproute2-next v2 1/6] bridge: support for controlling flooding of broadcast " Joachim Wiberg
2022-03-09 7:17 ` [PATCH iproute2-next v2 2/6] man: bridge: document new bcast_flood flag for bridge ports Joachim Wiberg
2022-03-09 7:17 ` [PATCH iproute2-next v2 3/6] ip: iplink_bridge_slave: support for broadcast flooding Joachim Wiberg
2022-03-09 7:17 ` [PATCH iproute2-next v2 4/6] man: ip-link: document new bcast_flood flag on bridge ports Joachim Wiberg
2022-03-09 7:28 ` Stephen Hemminger [this message]
2022-03-09 12:34 ` Joachim Wiberg
2022-03-09 7:17 ` [PATCH iproute2-next v2 5/6] man: ip-link: mention bridge port's default mcast_flood state Joachim Wiberg
2022-03-09 7:17 ` [PATCH iproute2-next v2 6/6] man: ip-link: whitespace fixes to odd line breaks mid sentence Joachim Wiberg
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=20220308232812.5dc9e7f5@hermes.local \
--to=stephen@networkplumber.org \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=troglobit@gmail.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).