From: Petr Machata <petrm@nvidia.com>
To: <netdev@vger.kernel.org>, <dsahern@gmail.com>,
<stephen@networkplumber.org>
Cc: Nikolay Aleksandrov <razor@blackwall.org>,
Ido Schimmel <idosch@nvidia.com>, Petr Machata <petrm@nvidia.com>
Subject: [PATCH iproute2-next 0/3] bridge: Support mcast_n_groups, mcast_max_groups
Date: Mon, 6 Feb 2023 18:50:24 +0100 [thread overview]
Message-ID: <cover.1675705077.git.petrm@nvidia.com> (raw)
In the Linux kernel commit cb3086cee656 ("Merge branch
'bridge-mdb-limit'"), the bridge driver gained support for limiting number
of MDB entries that a given port or port-VLAN is a member of. Support these
new attributes in iproute2's bridge tool.
After syncing the two relevant headers in patch #1, patch #2 introduces the
meat of the support, and patch #3 the man page coverage.
An example command line session is shown in patch #2.
Petr Machata (3):
uapi: Update if_bridge, if_link
bridge: Add support for mcast_n_groups, mcast_max_groups
man: man8: bridge: Describe mcast_max_groups
bridge/link.c | 21 +++++++++++++++++++++
bridge/vlan.c | 20 ++++++++++++++++++++
include/uapi/linux/if_bridge.h | 2 ++
include/uapi/linux/if_link.h | 5 +++++
man/man8/bridge.8 | 22 ++++++++++++++++++++++
5 files changed, 70 insertions(+)
--
2.39.0
next reply other threads:[~2023-02-06 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 17:50 Petr Machata [this message]
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
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=cover.1675705077.git.petrm@nvidia.com \
--to=petrm@nvidia.com \
--cc=dsahern@gmail.com \
--cc=idosch@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.