From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, noren@nvidia.com,
shuah@kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: drv-net: bump the timeout to 15min
Date: Mon, 17 Aug 2026 16:46:09 -0700 [thread overview]
Message-ID: <20260817164609.2c97cb0c@kernel.org> (raw)
In-Reply-To: <20260812171302.1888667-1-kuba@kernel.org>
On Wed, 12 Aug 2026 10:13:02 -0700 Jakub Kicinski wrote:
> 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.
The gve runner takes 20min on this test. It's getting impractical.
Let me send a series - this patch plus a patch to break gro up
into subtests.
--
pw-bot: cr
prev parent reply other threads:[~2026-08-17 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 17:13 [PATCH net-next] selftests: drv-net: bump the timeout to 15min Jakub Kicinski
2026-08-13 8:04 ` Nimrod Oren
2026-08-14 19:20 ` Jakub Kicinski
2026-08-17 23:46 ` Jakub Kicinski [this message]
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=20260817164609.2c97cb0c@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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