From: Paolo Abeni <pabeni@redhat.com>
To: Tariq Toukan <tariqt@nvidia.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>
Cc: Donald Hunter <donald.hunter@gmail.com>,
Jiri Pirko <jiri@resnulli.us>, Jonathan Corbet <corbet@lwn.net>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>, Mark Bloch <mbloch@nvidia.com>,
Shuah Khan <shuah@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kselftest@vger.kernel.org, Gal Pressman <gal@nvidia.com>,
Moshe Shemesh <moshe@nvidia.com>, Shay Drori <shayd@nvidia.com>,
Jiri Pirko <jiri@nvidia.com>, Or Har-Toov <ohartoov@nvidia.com>
Subject: Re: [PATCH net-next 4/5] selftest: netdevsim: Add devlink port resource test
Date: Tue, 3 Feb 2026 11:16:45 +0100 [thread overview]
Message-ID: <ce09e17d-2b74-4bda-a8ec-352c92659a6e@redhat.com> (raw)
In-Reply-To: <20260203071033.1709445-5-tariqt@nvidia.com>
On 2/3/26 8:10 AM, Tariq Toukan wrote:
> From: Or Har-Toov <ohartoov@nvidia.com>
>
> Add selftest to verify port-level resource functionality using netdevsim.
>
> Signed-off-by: Or Har-Toov <ohartoov@nvidia.com>
> Reviewed-by: Shay Drori <shayd@nvidia.com>
> Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
> ---
> .../drivers/net/netdevsim/devlink.sh | 32 ++++++++++++++++++-
> 1 file changed, 31 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/drivers/net/netdevsim/devlink.sh b/tools/testing/selftests/drivers/net/netdevsim/devlink.sh
> index 1b529ccaf050..674f0e981ab0 100755
> --- a/tools/testing/selftests/drivers/net/netdevsim/devlink.sh
> +++ b/tools/testing/selftests/drivers/net/netdevsim/devlink.sh
> @@ -5,7 +5,7 @@ lib_dir=$(dirname $0)/../../../net/forwarding
>
> ALL_TESTS="fw_flash_test params_test \
> params_default_test regions_test reload_test \
> - netns_reload_test resource_test dev_info_test \
> + netns_reload_test resource_test port_resource_test dev_info_test \
> empty_reporter_test dummy_reporter_test rate_test"
> NUM_NETIFS=0
> source $lib_dir/lib.sh
> @@ -856,6 +856,36 @@ rate_test()
> log_test "rate test"
> }
>
> +port_resource_test()
> +{
> + RET=0
> +
> + local first_port="${DL_HANDLE}/0"
> + local name
> + local size
> +
> + devlink port resource show "$first_port" > /dev/null 2>&1
> + check_err $? "Failed to show port resource for $first_port"
> +
> + name=$(cmd_jq "devlink port resource show $first_port -j" \
> + ".[][][].name")
> + [ "$name" == "max_sfs" ]
> + check_err $? "Unexpected resource name $name (expected max_sfs)"
> +
> + size=$(cmd_jq "devlink port resource show $first_port -j" \
> + ".[][][].size")
> + [ "$size" == "20" ]
> + check_err $? "Unexpected resource size $size (expected 20)"
> +
> + devlink port resource show "$DL_HANDLE" > /dev/null 2>&1
> + check_err $? "Failed to show port resources for $DL_HANDLE"
> +
> + devlink port resource show > /dev/null 2>&1
> + check_err $? "Failed to dump all port resources"
> +
> + log_test "port resource test"
> +}
> +
> setup_prepare()
> {
> modprobe netdevsim
This test is failing in NIPA (adding some more context beyond the
failing test output just in case it may help):
# Error: netdevsim: Exceeded number of supported fib entries.
# Error: netdevsim: Exceeded number of supported fib entries.
# kernel answers: Operation not permitted
# TEST: resource test [ OK ]
# Command "resource" not found
# Command "resource" not found
# TEST: port resource test [FAIL]
# Failed to show port resource for netdevsim/netdevsim10/0
# TEST: dev_info test [ OK ]
# TEST: empty reporter test [ OK ]
# kernel answers: Success
# kernel answers: Success
# ./devlink.sh: line 614: echo: write error: Invalid argument
# Error: netdevsim: User setup the recover to fail for testing purposes.
/P
next prev parent reply other threads:[~2026-02-03 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 7:10 [PATCH net-next 0/5] devlink: add per-port resource support Tariq Toukan
2026-02-03 7:10 ` [PATCH net-next 1/5] devlink: Add port-level resource infrastructure Tariq Toukan
2026-02-04 9:51 ` Jiri Pirko
2026-02-05 15:26 ` Or Har-Toov
2026-02-04 9:58 ` Jiri Pirko
2026-02-03 7:10 ` [PATCH net-next 2/5] net/mlx5: Register SF resource on PF port representor Tariq Toukan
2026-02-03 7:10 ` [PATCH net-next 3/5] netdevsim: Add devlink port resource registration Tariq Toukan
2026-02-04 9:54 ` Jiri Pirko
2026-02-03 7:10 ` [PATCH net-next 4/5] selftest: netdevsim: Add devlink port resource test Tariq Toukan
2026-02-03 10:16 ` Paolo Abeni [this message]
2026-02-04 2:26 ` Jakub Kicinski
2026-02-04 7:08 ` Tariq Toukan
2026-02-03 7:10 ` [PATCH net-next 5/5] devlink: Document port-level resources Tariq Toukan
2026-02-04 9:56 ` Jiri Pirko
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=ce09e17d-2b74-4bda-a8ec-352c92659a6e@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=ohartoov@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--cc=shuah@kernel.org \
--cc=tariqt@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