From: Jacob Keller <jacob.e.keller@intel.com>
To: Petr Machata <petrm@nvidia.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<netdev@vger.kernel.org>
Cc: Ido Schimmel <idosch@nvidia.com>,
Wentao Liang <vulab@iscas.ac.cn>, <mlxsw@nvidia.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH net 2/2] selftests: mlxsw: Test port range occupancy on template create
Date: Tue, 6 Oct 2026 14:50:34 -0700 [thread overview]
Message-ID: <20d04737-6080-42e4-9a1c-c1a8673dddf8@intel.com> (raw)
In-Reply-To: <e7b37b80adb7ac8b0ef20a22d7654a6656c1c545.1791294384.git.petrm@nvidia.com>
On 10/6/2026 7:21 AM, Petr Machata wrote:
> Add a test that creates a tc chain template matching on both source and
> destination port ranges and verifies via devlink-resource occupancy that
> this does not leak port range registers, neither while the template
> exists nor after it is deleted.
>
Nice to see this covered by a selftest :D
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
Thanks,
Jake
> Assisted-by: LLM
> Reviewed-by: Ido Schimmel <idosch@nvidia.com>
> Signed-off-by: Petr Machata <petrm@nvidia.com>
> ---
> .../drivers/net/mlxsw/port_range_occ.sh | 26 +++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/tools/testing/selftests/drivers/net/mlxsw/port_range_occ.sh b/tools/testing/selftests/drivers/net/mlxsw/port_range_occ.sh
> index b1f0781f6b25..c7eba3f15066 100755
> --- a/tools/testing/selftests/drivers/net/mlxsw/port_range_occ.sh
> +++ b/tools/testing/selftests/drivers/net/mlxsw/port_range_occ.sh
> @@ -9,6 +9,7 @@ lib_dir=$(dirname $0)/../../../net/forwarding
>
> ALL_TESTS="
> port_range_occ_test
> + port_range_occ_tmplt_test
> "
> NUM_NETIFS=2
> source $lib_dir/lib.sh
> @@ -101,6 +102,31 @@ port_range_occ_test()
> log_test "port range occupancy"
> }
>
> +port_range_occ_tmplt_test()
> +{
> + local occ
> +
> + RET=0
> + occ=$(port_range_occ_get)
> +
> + # Addition of a chain template should not impact occupancy.
> + tc chain add dev "$swp1" ingress chain 1 protocol ip \
> + flower ip_proto udp src_port 501-600 dst_port 701-800
> + check_err $? "Could not add chain template"
> +
> + (( occ == $(port_range_occ_get) ))
> + check_err $? "Got occupancy $(port_range_occ_get), expected $occ"
> +
> + # And just for completeness sake, neither should deletion.
> + tc chain del dev "$swp1" ingress chain 1
> + check_err $? "Could not delete chain template"
> +
> + (( occ == $(port_range_occ_get) ))
> + check_err $? "Got occupancy $(port_range_occ_get), expected $occ"
> +
> + log_test "port range occupancy after template create/destroy"
> +}
> +
> trap cleanup EXIT
>
> setup_prepare
next prev parent reply other threads:[~2026-10-06 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 14:21 [PATCH net 0/2] mlxsw: Fix port range register leak Petr Machata
2026-10-06 14:21 ` [PATCH net 1/2] mlxsw: spectrum_flower: Fix port range register leak in tmplt_create() Petr Machata
2026-10-06 21:49 ` Jacob Keller
2026-10-06 14:21 ` [PATCH net 2/2] selftests: mlxsw: Test port range occupancy on template create Petr Machata
2026-10-06 21:50 ` Jacob Keller [this message]
2026-10-08 18:00 ` [PATCH net 0/2] mlxsw: Fix port range register leak 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=20d04737-6080-42e4-9a1c-c1a8673dddf8@intel.com \
--to=jacob.e.keller@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--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=shuah@kernel.org \
--cc=vulab@iscas.ac.cn \
/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