The GRO test takes extra time on NICs which support HW-GRO and LRO
(as it also runs the test cases against the NIC implementation).
gro.py takes 6min on bnxt and 10min on mlx5 with debug kernel builds.
The delta between drivers is to some extent due to their defaults
(mlx5 sillily defaults to queue-per-thread, while bnxt follows
netif_get_num_default_rss_queues()).
At the end of the day the defaults don't matter much - on larger
machines all drivers will create more queues. We should bump
the timeout. Let's give ourselves a 50% margin over mlx5's needs
and set the timeout to 15min.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
CC: noren@nvidia.com
CC: shuah@kernel.org
CC: linux-kselftest@vger.kernel.org
---
tools/testing/selftests/drivers/net/settings | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/drivers/net/settings b/tools/testing/selftests/drivers/net/settings
index eef533824a3c..e2206265f67c 100644
--- a/tools/testing/selftests/drivers/net/settings
+++ b/tools/testing/selftests/drivers/net/settings
@@ -1 +1 @@
-timeout=360
+timeout=900
--
2.55.0