[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e69754d3-dead-5477-266b-8618f567ac34@blackwall.org>
Date: Thu, 9 Feb 2023 09:24:11 +0100
From: Nikolay Aleksandrov <razor@...ckwall.org>
To: Ido Schimmel <idosch@...dia.com>, netdev@...r.kernel.org,
bridge@...ts.linux-foundation.org
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
edumazet@...gle.com, roopa@...dia.com, petrm@...dia.com,
mlxsw@...dia.com
Subject: Re: [PATCH net-next 4/4] selftests: forwarding: Add MDB dump test
cases
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@...dia.com>
> Reviewed-by: Petr Machata <petrm@...dia.com>
> ---
> .../selftests/net/forwarding/bridge_mdb.sh | 99 +++++++++++++++++++
> 1 file changed, 99 insertions(+)
>
Nice!
Acked-by: Nikolay Aleksandrov <razor@...ckwall.org>
Powered by blists - more mailing lists