From: patchwork-bot+netdevbpf@kernel.org
To: Johannes Nixdorf <jnixdorf-oss@avm.de>
Cc: dsahern@gmail.com, roopa@nvidia.com, razor@blackwall.org,
idosch@nvidia.com, petrm@nvidia.com,
bridge@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next v5] iplink: bridge: Add support for bridge FDB learning limits
Date: Thu, 19 Oct 2023 15:40:22 +0000 [thread overview]
Message-ID: <169773002236.10915.7572793107235329470.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231018-fdb_limit-v5-1-7ca3b3eb7c1f@avm.de>
Hello:
This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Wed, 18 Oct 2023 09:04:43 +0200 you wrote:
> Support setting the FDB limit through ip link. The arguments is:
> - fdb_max_learned: A 32-bit unsigned integer specifying the maximum
> number of learned FDB entries, with 0 disabling
> the limit.
>
> Also support reading back the current number of learned FDB entries in
> the bridge by this count. The returned value's name is:
> - fdb_n_learned: A 32-bit unsigned integer specifying the current number
> of learned FDB entries.
>
> [...]
Here is the summary with links:
- [iproute2-next,v5] iplink: bridge: Add support for bridge FDB learning limits
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=48cb4320487a
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-19 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 7:04 [PATCH iproute2-next v5] iplink: bridge: Add support for bridge FDB learning limits Johannes Nixdorf
2023-10-19 9:50 ` Petr Machata
2023-10-19 13:12 ` Nikolay Aleksandrov
2023-10-19 15:40 ` 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=169773002236.10915.7572793107235329470.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=dsahern@gmail.com \
--cc=idosch@nvidia.com \
--cc=jnixdorf-oss@avm.de \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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).