From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
shuah@kernel.org, willemb@google.com, petrm@nvidia.com,
linux-kselftest@vger.kernel.org, noren@nvidia.com, joe@dama.to
Subject: Re: [PATCH net-next v2 0/3] selftests: drv-net: split up gro.py
Date: Thu, 03 Sep 2026 01:40:52 +0000 [thread overview]
Message-ID: <178839965238.3035212.7952345035477663016.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260901200728.2063720-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 1 Sep 2026 13:07:25 -0700 you wrote:
> gro.py runs its full set of cases three times over - against SW GRO,
> HW GRO and LRO. It's our test with the longest runtime. The 318 cases
> take 12m30s on mlx5 with a debug kernel.
>
> We will likely add more subcases here as the time goes on, so it's
> time to start splitting it up. Long runtime wastes time on retries
> (if any of the 300+ cases fails we try to check if it's a real failure
> or flake an re-run the whole thing). It also forces us to increase
> timeout for the whole test suite.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/3] selftests: drv-net: hw: rename gro_hw.py to gro_stats.py
https://git.kernel.org/netdev/net-next/c/889b0cca6b29
- [net-next,v2,2/3] selftests: drv-net: split gro.py into one test per coalescing mode
https://git.kernel.org/netdev/net-next/c/f225a7317c18
- [net-next,v2,3/3] selftests: drv-net: bump the timeout to 15min
https://git.kernel.org/netdev/net-next/c/34d89dee719b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-03 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 20:07 [PATCH net-next v2 0/3] selftests: drv-net: split up gro.py Jakub Kicinski
2026-09-01 20:07 ` [PATCH net-next v2 1/3] selftests: drv-net: hw: rename gro_hw.py to gro_stats.py Jakub Kicinski
2026-09-01 20:07 ` [PATCH net-next v2 2/3] selftests: drv-net: split gro.py into one test per coalescing mode Jakub Kicinski
2026-09-01 20:07 ` [PATCH net-next v2 3/3] selftests: drv-net: bump the timeout to 15min Jakub Kicinski
2026-09-03 1:40 ` patchwork-bot+netdevbpf [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=178839965238.3035212.7952345035477663016.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=joe@dama.to \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=shuah@kernel.org \
--cc=willemb@google.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