From: Nikolay Aleksandrov <razor@blackwall.org>
To: Johannes Nixdorf <jnixdorf-oss@avm.de>,
bridge@lists.linux-foundation.org
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Ido Schimmel <idosch@nvidia.com>, David Ahern <dsahern@gmail.com>,
Roopa Prabhu <roopa@nvidia.com>,
Oleksij Rempel <linux@rempel-privat.de>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Bridge] [PATCH net-next v2 3/3] net: bridge: Add a configurable default FDB learning limit
Date: Tue, 20 Jun 2023 09:56:06 +0300 [thread overview]
Message-ID: <3fdb4091-3dc9-e1f2-26a6-561c021c9fae@blackwall.org> (raw)
In-Reply-To: <20230619071444.14625-4-jnixdorf-oss@avm.de>
On 6/19/23 10:14, Johannes Nixdorf wrote:
> This adds a Kconfig option to configure a default FDB learning limit
> system wide, so a distributor building a special purpose kernel can
> limit all created bridges by default.
>
> The limit is only a soft default setting and overridable per bridge
> using netlink.
>
> Signed-off-by: Johannes Nixdorf <jnixdorf-oss@avm.de>
>
> ---
>
> Changes since v1:
> - Added a default limit in Kconfig. (deemed acceptable in review
> comments)
>
> net/bridge/Kconfig | 13 +++++++++++++
> net/bridge/br_device.c | 2 ++
> 2 files changed, 15 insertions(+)
>
> diff --git a/net/bridge/Kconfig b/net/bridge/Kconfig
> index 3c8ded7d3e84..c0d9c08088c4 100644
> --- a/net/bridge/Kconfig
> +++ b/net/bridge/Kconfig
> @@ -84,3 +84,16 @@ config BRIDGE_CFM
> Say N to exclude this support and reduce the binary size.
>
> If unsure, say N.
> +
> +config BRIDGE_DEFAULT_FDB_MAX_LEARNED
> + int "Default FDB learning limit"
> + default 0
> + depends on BRIDGE
> + help
> + Sets a default limit on the number of learned FDB entries on
> + new bridges. This limit can be overwritten via netlink on a
> + per bridge basis.
> +
> + The default of 0 disables the limit.
> +
> + If unsure, say 0.
> diff --git a/net/bridge/br_device.c b/net/bridge/br_device.c
> index 8eca8a5c80c6..93f081ce8195 100644
> --- a/net/bridge/br_device.c
> +++ b/net/bridge/br_device.c
> @@ -530,6 +530,8 @@ void br_dev_setup(struct net_device *dev)
> br->bridge_ageing_time = br->ageing_time = BR_DEFAULT_AGEING_TIME;
> dev->max_mtu = ETH_MAX_MTU;
>
> + br->fdb_max_learned_entries = CONFIG_BRIDGE_DEFAULT_FDB_MAX_LEARNED;
> +
> br_netfilter_rtable_init(br);
> br_stp_timer_init(br);
> br_multicast_init(br);
IMO this is pointless, noone will set the kconfig option except very
specific users. I prefer if we leave it to the distribution to set a
maximum on bridge creation, i.e. make it a distro policy.
next prev parent reply other threads:[~2023-06-20 6:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 7:14 [Bridge] [PATCH net-next v2 0/3, iproute2-next 0/1] bridge: Add a limit on learned FDB entries Johannes Nixdorf
2023-06-19 7:14 ` [Bridge] [PATCH net-next v2 1/3] bridge: Set BR_FDB_ADDED_BY_USER early in fdb_add_entry Johannes Nixdorf
2023-06-19 14:50 ` Ido Schimmel
2023-06-19 7:14 ` [Bridge] [PATCH net-next v2 2/3] bridge: Add a limit on learned FDB entries Johannes Nixdorf
2023-06-19 15:34 ` Ido Schimmel
2023-06-20 6:55 ` Nikolay Aleksandrov
2023-06-20 13:35 ` Johannes Nixdorf
2023-06-22 12:27 ` Nikolay Aleksandrov
2023-06-22 12:39 ` Nikolay Aleksandrov
2023-06-19 7:14 ` [Bridge] [PATCH net-next v2 3/3] net: bridge: Add a configurable default FDB learning limit Johannes Nixdorf
2023-06-20 6:56 ` Nikolay Aleksandrov [this message]
2023-06-19 7:14 ` [Bridge] [PATCH iproute2-next 1/1] iplink: bridge: Add support for bridge FDB learning limits Johannes Nixdorf
2023-06-19 14:37 ` 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=3fdb4091-3dc9-e1f2-26a6-561c021c9fae@blackwall.org \
--to=razor@blackwall.org \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=idosch@nvidia.com \
--cc=jnixdorf-oss@avm.de \
--cc=kuba@kernel.org \
--cc=linux@rempel-privat.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roopa@nvidia.com \
--cc=vladimir.oltean@nxp.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