From: Nikolay Aleksandrov <razor@blackwall.org>
To: Ido Schimmel <idosch@nvidia.com>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Cc: petrm@nvidia.com, mlxsw@nvidia.com, edumazet@google.com,
roopa@nvidia.com, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Bridge] [PATCH net-next 4/4] selftests: forwarding: Add MDB dump test cases
Date: Thu, 9 Feb 2023 09:24:11 +0100 [thread overview]
Message-ID: <e69754d3-dead-5477-266b-8618f567ac34@blackwall.org> (raw)
In-Reply-To: <20230209071852.613102-5-idosch@nvidia.com>
On 2/9/23 09:18, Ido Schimmel wrote:
> The kernel maintains three markers for the MDB dump:
>
> 1. The last bridge device from which the MDB was dumped.
> 2. The last MDB entry from which the MDB was dumped.
> 3. The last port-group entry that was dumped.
>
> Add test cases for large scale MDB dump to make sure that all the
> configured entries are dumped and that the markers are used correctly.
>
> Specifically, create 2 bridges with 32 ports and add 256 MDB entries in
> which all the ports are member of. Test that each bridge reports 8192
> (256 * 32) permanent entries. Do that with IPv4, IPv6 and L2 MDB
> entries.
>
> On my system, MDB dump of the above is contained in about 50 netlink
> messages.
>
> Example output:
>
> # ./bridge_mdb.sh
> [...]
> INFO: # Large scale dump tests
> TEST: IPv4 large scale dump tests [ OK ]
> TEST: IPv6 large scale dump tests [ OK ]
> TEST: L2 large scale dump tests [ OK ]
> [...]
>
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> Reviewed-by: Petr Machata <petrm@nvidia.com>
> ---
> .../selftests/net/forwarding/bridge_mdb.sh | 99 +++++++++++++++++++
> 1 file changed, 99 insertions(+)
>
Nice!
Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
next prev parent reply other threads:[~2023-02-09 8:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 7:18 [Bridge] [PATCH net-next 0/4] bridge: mcast: Preparations for VXLAN MDB Ido Schimmel
2023-02-09 7:18 ` [Bridge] [PATCH net-next 1/4] bridge: mcast: Use correct define in MDB dump Ido Schimmel
2023-02-09 8:18 ` Nikolay Aleksandrov
2023-02-09 7:18 ` [Bridge] [PATCH net-next 2/4] bridge: mcast: Remove pointless sequence generation counter assignment Ido Schimmel
2023-02-09 8:19 ` Nikolay Aleksandrov
2023-02-09 7:18 ` [Bridge] [PATCH net-next 3/4] bridge: mcast: Move validation to a policy Ido Schimmel
2023-02-09 8:23 ` Nikolay Aleksandrov
2023-02-11 3:20 ` Jakub Kicinski
2023-02-11 15:45 ` Ido Schimmel
2023-02-09 7:18 ` [Bridge] [PATCH net-next 4/4] selftests: forwarding: Add MDB dump test cases Ido Schimmel
2023-02-09 8:24 ` Nikolay Aleksandrov [this message]
2023-02-11 3:40 ` [Bridge] [PATCH net-next 0/4] bridge: mcast: Preparations for VXLAN MDB patchwork-bot+netdevbpf
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=e69754d3-dead-5477-266b-8618f567ac34@blackwall.org \
--to=razor@blackwall.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--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