diff options
author | 2022-06-28 12:37:44 +0200 | |
---|---|---|
committer | 2022-06-29 14:01:23 +0100 | |
commit | 04cfbc1d89d4cc73b5b328e3bacf24d43e9aa4b7 (patch) | |
tree | f6146a6db4c69fb83c5be65fc0d5a992a26994b3 /drivers/net/dsa/microchip | |
parent | nfp: flower: fix comment typos and formatting (diff) | |
download | linux-dev-04cfbc1d89d4cc73b5b328e3bacf24d43e9aa4b7.tar.xz linux-dev-04cfbc1d89d4cc73b5b328e3bacf24d43e9aa4b7.zip |
selftests: forwarding: ethtool_extended_state: Convert to busywait
Currently, this script sets up the test scenario, which is supposed to end
in an inability of the system to negotiate a link. It then waits for a bit,
and verifies that the system can diagnose why the link was not established.
The wait time for the scenario where different link speeds are forced on
the two ends of a loopback cable, was set to 4 seconds, which exactly
covered it. As of a recent mlxsw firmware update, this time gets longer,
and this test starts failing.
The time that selftests currently wait for links to be established is
currently $WAIT_TIMEOUT, or 20 seconds. It seems reasonable that if this is
the time necessary to establish and bring up a link, it should also be
enough to determine that a link cannot be established and why.
Therefore in this patch, convert the sleeps to busywaits, so that if a
failure is established sooner (as is expected), the test runs quicker. And
use $WAIT_TIMEOUT as the time to wait.
Signed-off-by: Petr Machata <petrm@nvidia.com>
Reviewed-by: Amit Cohen <amcohen@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/dsa/microchip')
0 files changed, 0 insertions, 0 deletions