From: patchwork-bot+netdevbpf@kernel.org
To: Johannes Nixdorf <jnixdorf-oss@avm.de>
Cc: andrew@lunn.ch, f.fainelli@gmail.com,
bridge@lists.linux-foundation.org, idosch@nvidia.com,
razor@blackwall.org, roopa@nvidia.com,
linux-kernel@vger.kernel.org, linux@rempel-privat.de,
vladimir.oltean@nxp.com, edumazet@google.com,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
dsahern@gmail.com, kuba@kernel.org, pabeni@redhat.com,
shuah@kernel.org, davem@davemloft.net
Subject: Re: [Bridge] [PATCH net-next v5 0/5] bridge: Add a limit on learned FDB entries
Date: Wed, 18 Oct 2023 01:00:30 +0000 [thread overview]
Message-ID: <169759083043.18882.3734658950123094755.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231016-fdb_limit-v5-0-32cddff87758@avm.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 16 Oct 2023 15:27:19 +0200 you wrote:
> Introduce a limit on the amount of learned FDB entries on a bridge,
> configured by netlink with a build time default on bridge creation in
> the kernel config.
>
> For backwards compatibility the kernel config default is disabling the
> limit (0).
>
> [...]
Here is the summary with links:
- [net-next,v5,1/5] net: bridge: Set BR_FDB_ADDED_BY_USER early in fdb_add_entry
https://git.kernel.org/netdev/net-next/c/cbf51acbc5d5
- [net-next,v5,2/5] net: bridge: Track and limit dynamically learned FDB entries
https://git.kernel.org/netdev/net-next/c/bdb4dfda3b41
- [net-next,v5,3/5] net: bridge: Add netlink knobs for number / max learned FDB entries
https://git.kernel.org/netdev/net-next/c/ddd1ad68826d
- [net-next,v5,4/5] net: bridge: Set strict_start_type for br_policy
https://git.kernel.org/netdev/net-next/c/19297c3ab23c
- [net-next,v5,5/5] selftests: forwarding: bridge_fdb_learning_limit: Add a new selftest
https://git.kernel.org/netdev/net-next/c/6f84090333bb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-18 1:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 13:27 [Bridge] [PATCH net-next v5 0/5] bridge: Add a limit on learned FDB entries Johannes Nixdorf
2023-10-16 13:27 ` [Bridge] [PATCH net-next v5 1/5] net: bridge: Set BR_FDB_ADDED_BY_USER early in fdb_add_entry Johannes Nixdorf
2023-10-16 13:27 ` [Bridge] [PATCH net-next v5 2/5] net: bridge: Track and limit dynamically learned FDB entries Johannes Nixdorf
2023-10-16 13:27 ` [Bridge] [PATCH net-next v5 3/5] net: bridge: Add netlink knobs for number / max " Johannes Nixdorf
2023-10-17 9:31 ` Nikolay Aleksandrov
2023-10-17 11:06 ` Ido Schimmel
2023-10-16 13:27 ` [Bridge] [PATCH net-next v5 4/5] net: bridge: Set strict_start_type for br_policy Johannes Nixdorf
2023-10-17 9:32 ` Nikolay Aleksandrov
2023-10-17 11:06 ` Ido Schimmel
2023-10-16 13:27 ` [Bridge] [PATCH net-next v5 5/5] selftests: forwarding: bridge_fdb_learning_limit: Add a new selftest Johannes Nixdorf
2023-10-18 1:00 ` patchwork-bot+netdevbpf [this message]
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=169759083043.18882.3734658950123094755.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.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-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=shuah@kernel.org \
--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