From: Joachim Wiberg <troglobit@gmail.com>
To: netdev@vger.kernel.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Nikolay Aleksandrov <razor@blackwall.org>,
Joachim Wiberg <troglobit@gmail.com>
Subject: [PATCH iproute2-next 0/2] bridge: support for controlling broadcast flooding per port
Date: Tue, 8 Mar 2022 14:29:13 +0100 [thread overview]
Message-ID: <20220308132915.2610480-1-troglobit@gmail.com> (raw)
Hi,
this patch set addresses a slight omission in controlling broadcast
flooding per bridge port, which the bridge has had support for a good
while now.
I've grouped the setting alongside it's cousin mcast_flood, but there
could be a need for some rearrangement to also move unicast flooding
to the same group.
Best regards
/Joachim
next reply other threads:[~2022-03-08 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 13:29 Joachim Wiberg [this message]
2022-03-08 13:29 ` [PATCH iproute2-next 1/2] bridge: support for controlling flooding of broadcast per port Joachim Wiberg
2022-03-08 16:11 ` Nikolay Aleksandrov
2022-03-09 6:14 ` Joachim Wiberg
2022-03-08 13:29 ` [PATCH iproute2-next 2/2] man: document new bcast_flood config/query support for bridge ports 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=20220308132915.2610480-1-troglobit@gmail.com \
--to=troglobit@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--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).