From: Petr Machata <petrm@nvidia.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: <netdev@vger.kernel.org>, <kuba@kernel.org>, <pabeni@redhat.com>,
<davem@davemloft.net>, <edumazet@google.com>, <parav@nvidia.com>,
<mst@redhat.com>, <jasowang@redhat.com>,
<xuanzhuo@linux.alibaba.com>, <shuah@kernel.org>,
<petrm@nvidia.com>, <liuhangbin@gmail.com>,
<vladimir.oltean@nxp.com>, <bpoirier@nvidia.com>,
<idosch@nvidia.com>, <virtualization@lists.linux.dev>
Subject: Re: [patch net-next v3 3/6] selftests: forwarding: add ability to assemble NETIFS array by driver name
Date: Thu, 18 Apr 2024 10:11:12 +0200 [thread overview]
Message-ID: <87bk67cbuc.fsf@nvidia.com> (raw)
In-Reply-To: <20240417164554.3651321-4-jiri@resnulli.us>
Jiri Pirko <jiri@resnulli.us> writes:
> From: Jiri Pirko <jiri@nvidia.com>
>
> Allow driver tests to work without specifying the netdevice names.
> Introduce a possibility to search for available netdevices according to
> set driver name. Allow test to specify the name by setting
> NETIF_FIND_DRIVER variable.
>
> Note that user overrides this either by passing netdevice names on the
> command line or by declaring NETIFS array in custom forwarding.config
> configuration file.
>
> Signed-off-by: Jiri Pirko <jiri@nvidia.com>
> ---
> v1->v2:
> - removed unnecessary "-p" and "-e" options
> - removed unnecessary "! -z" from the check
> - moved NETIF_FIND_DRIVER declaration from the config options
> ---
> tools/testing/selftests/net/forwarding/lib.sh | 39 +++++++++++++++++++
> 1 file changed, 39 insertions(+)
>
> diff --git a/tools/testing/selftests/net/forwarding/lib.sh b/tools/testing/selftests/net/forwarding/lib.sh
> index 2e7695b94b6b..b3fd0f052d71 100644
> --- a/tools/testing/selftests/net/forwarding/lib.sh
> +++ b/tools/testing/selftests/net/forwarding/lib.sh
> @@ -94,6 +94,45 @@ if [[ ! -v NUM_NETIFS ]]; then
> exit $ksft_skip
> fi
>
> +##############################################################################
> +# Find netifs by test-specified driver name
> +
> +driver_name_get()
> +{
> + local dev=$1; shift
> + local driver_path="/sys/class/net/$dev/device/driver"
> +
> + if [ ! -L $driver_path ]; then
> + echo ""
> + else
> + basename `realpath $driver_path`
> + fi
This is just:
if [[ -L $driver_path ]]; then
basename `realpath $driver_path`
fi
> +}
> +
> +find_netif()
Maybe name it find_driver_netif? find_netif sounds super generic.
Also consider having it take an argument instead of accessing
environment NETIF_FIND_DRIVER directly.
> +{
> + local ifnames=`ip -j link show | jq -r ".[].ifname"`
> + local count=0
> +
> + for ifname in $ifnames
> + do
> + local driver_name=`driver_name_get $ifname`
> + if [[ ! -z $driver_name && $driver_name == $NETIF_FIND_DRIVER ]]; then
> + count=$((count + 1))
> + NETIFS[p$count]="$ifname"
> + fi
> + done
> +}
> +
> +# Whether to find netdevice according to the specified driver.
> +: "${NETIF_FIND_DRIVER:=}"
This would be better placed up there in the Topology description
section. Together with NETIFS and NETIF_NO_CABLE, as it concerns
specification of which interfaces to use.
> +
> +if [[ $NETIF_FIND_DRIVER ]]; then
> + unset NETIFS
> + declare -A NETIFS
> + find_netif
> +fi
> +
> net_forwarding_dir=$(dirname "$(readlink -e "${BASH_SOURCE[0]}")")
>
> if [[ -f $net_forwarding_dir/forwarding.config ]]; then
next prev parent reply other threads:[~2024-04-18 8:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 16:45 [patch net-next v3 0/6] selftests: virtio_net: introduce initial testing infrastructure Jiri Pirko
2024-04-17 16:45 ` [patch net-next v3 1/6] virtio: add debugfs infrastructure to allow to debug virtio features Jiri Pirko
2024-04-17 16:45 ` [patch net-next v3 2/6] selftests: forwarding: move couple of initial check to the beginning Jiri Pirko
2024-04-17 18:58 ` Benjamin Poirier
2024-04-18 6:16 ` Jiri Pirko
2024-04-17 16:45 ` [patch net-next v3 3/6] selftests: forwarding: add ability to assemble NETIFS array by driver name Jiri Pirko
2024-04-18 8:11 ` Petr Machata [this message]
2024-04-18 8:43 ` Petr Machata
2024-04-18 12:01 ` Jiri Pirko
2024-04-18 12:14 ` Jiri Pirko
2024-04-17 16:45 ` [patch net-next v3 4/6] selftests: forwarding: add check_driver() helper Jiri Pirko
2024-04-18 8:31 ` Petr Machata
2024-04-17 16:45 ` [patch net-next v3 5/6] selftests: forwarding: add wait_for_dev() helper Jiri Pirko
2024-04-18 8:33 ` Petr Machata
2024-04-18 12:01 ` Jiri Pirko
2024-04-17 16:45 ` [patch net-next v3 6/6] selftests: virtio_net: add initial tests Jiri Pirko
2024-04-18 8:39 ` Petr Machata
2024-04-18 12:00 ` 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=87bk67cbuc.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=bpoirier@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=jasowang@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=shuah@kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=vladimir.oltean@nxp.com \
--cc=xuanzhuo@linux.alibaba.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).