From: Jiri Pirko <jiri@resnulli.us>
To: Benjamin Poirier <benjamin.poirier@gmail.com>
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, idosch@nvidia.com,
virtualization@lists.linux.dev
Subject: Re: [patch net-next 5/6] selftests: forwarding: add wait_for_dev() helper
Date: Sat, 13 Apr 2024 15:29:08 +0200 [thread overview]
Message-ID: <ZhqIpIF5N1ESWgON@nanopsycho> (raw)
In-Reply-To: <Zhmc_KsL__7noHWZ@f4>
Fri, Apr 12, 2024 at 10:43:40PM CEST, benjamin.poirier@gmail.com wrote:
>On 2024-04-12 17:13 +0200, Jiri Pirko wrote:
>> From: Jiri Pirko <jiri@nvidia.com>
>>
>> The existing setup_wait*() helper family check the status of the
>> interface to be up. Introduce wait_for_dev() to wait for the netdevice
>> to appear, for example after test script does manual device bind.
>>
>> Signed-off-by: Jiri Pirko <jiri@nvidia.com>
>> ---
>> tools/testing/selftests/net/forwarding/lib.sh | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>>
>> diff --git a/tools/testing/selftests/net/forwarding/lib.sh b/tools/testing/selftests/net/forwarding/lib.sh
>> index 959183b516ce..74859f969997 100644
>> --- a/tools/testing/selftests/net/forwarding/lib.sh
>> +++ b/tools/testing/selftests/net/forwarding/lib.sh
>> @@ -746,6 +746,25 @@ setup_wait()
>> sleep $WAIT_TIME
>> }
>>
>> +wait_for_dev()
>> +{
>> + local dev=$1; shift
>> + local timeout=${1:-$WAIT_TIMEOUT}; shift
>> + local max_iterations=$(($timeout * 10))
>> +
>> + for ((i = 1; i <= $max_iterations; ++i)); do
>> + ip link show dev $dev up &> /dev/null
>> + if [[ $? -ne 0 ]]; then
>> + sleep 0.1
>> + else
>> + return 0
>> + fi
>> + done
>> +
>> + log_test wait_for_dev ": Interface $dev did not appear."
>> + exit 1
>> +}
>
>How about rewriting the function to make use of the `slowwait` helper as
>follows:
>
>wait_for_dev()
>{
> local dev=$1; shift
> local timeout=${1:-$WAIT_TIMEOUT}; shift
>
> slowwait $timeout ip link show dev $dev up &> /dev/null
> if (( $? )); then
> check_err 1
> log_test wait_for_dev "Interface $dev did not appear."
> exit $EXIT_STATUS
> fi
>}
Sure, will redo this. Thanks!
next prev parent reply other threads:[~2024-04-13 13:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 15:13 [patch net-next 0/6] selftests: virtio_net: introduce initial testing infrastructure Jiri Pirko
2024-04-12 15:13 ` [patch net-next 1/6] virtio: add debugfs infrastructure to allow to debug virtio features Jiri Pirko
2024-04-12 15:13 ` [patch net-next 2/6] selftests: forwarding: move couple of initial check to the beginning Jiri Pirko
2024-04-12 15:13 ` [patch net-next 3/6] selftests: forwarding: add ability to assemble NETIFS array by driver name Jiri Pirko
2024-04-12 20:38 ` Benjamin Poirier
2024-04-13 13:27 ` Jiri Pirko
2024-04-14 19:32 ` Benjamin Poirier
2024-04-15 8:40 ` Jiri Pirko
2024-04-12 15:13 ` [patch net-next 4/6] selftests: forwarding: add check_driver() helper Jiri Pirko
2024-04-12 15:13 ` [patch net-next 5/6] selftests: forwarding: add wait_for_dev() helper Jiri Pirko
2024-04-12 20:43 ` Benjamin Poirier
2024-04-13 13:29 ` Jiri Pirko [this message]
2024-04-12 15:13 ` [patch net-next 6/6] selftests: virtio_net: add initial tests Jiri Pirko
2024-04-12 20:46 ` Benjamin Poirier
2024-04-13 13:29 ` Jiri Pirko
2024-04-13 1:04 ` [patch net-next 0/6] selftests: virtio_net: introduce initial testing infrastructure Jakub Kicinski
2024-04-13 13:23 ` Jiri Pirko
2024-04-15 17:26 ` Jakub Kicinski
2024-04-16 9:53 ` Jiri Pirko
2024-04-16 13:03 ` Jiri Pirko
2024-04-17 4:36 ` Jason Wang
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=ZhqIpIF5N1ESWgON@nanopsycho \
--to=jiri@resnulli.us \
--cc=benjamin.poirier@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=jasowang@redhat.com \
--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=petrm@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).