From: Jakub Kicinski <kuba@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
shuah@kernel.org, sdf@fomichev.me, krakauer@google.com,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 00/12] selftests: drv-net: convert GRO and Toeplitz tests to work for drivers in NIPA
Date: Mon, 17 Nov 2025 20:56:09 -0800 [thread overview]
Message-ID: <20251117205609.4b0fa035@kernel.org> (raw)
In-Reply-To: <willemdebruijn.kernel.31c286e47985d@gmail.com>
On Mon, 17 Nov 2025 21:11:31 -0500 Willem de Bruijn wrote:
> > Note that neither GRO nor the Toeplitz test fully passes for me on
> > any HW I have access to. But this is unrelated to the conversion.
>
> You observed the same failures with the old and new tests? Are they
> deterministic failures or flakes.
Deterministic for Toeplitz - all NICs I have calculate the Rx
hash the same as the test for at least one of traffic types.
But none of them exactly as the test is expecting.
One IIRC also uses non-standard RSS indir table pattern by default.
The indirection table will be a trivial fix.
For HW-GRO I investigated less closely I mostly focused on making sure
netdevsim is solid as a replacement for veth. There was more flakiness
on HW (admittedly I was running inter-dc-building). But the failures
looked rather sus - the test was reporting that packets which were
not supposed to be coalesced got coalesced.
BTW it's slightly inconvenient that we disable HW-GRO when normal GRO
is disabled :( Makes it quite hard to run the test to check device
behavior. My current plan is to rely on device counters to check
whether traffic is getting coalesced but better ideas most welcome :(
> > This series is not making any real functional changes to the tests,
> > it is limited to improving the "test harness" scripts.
>
> No significant actionable comments, just a few trivial typos.
Thanks!
next prev parent reply other threads:[~2025-11-18 4:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 20:57 [PATCH net-next 00/12] selftests: drv-net: convert GRO and Toeplitz tests to work for drivers in NIPA Jakub Kicinski
2025-11-17 20:57 ` [PATCH net-next 01/12] selftests: net: py: coding style improvements Jakub Kicinski
2025-11-17 20:58 ` [PATCH net-next 02/12] selftests: net: py: extract the case generation logic Jakub Kicinski
2025-11-17 20:58 ` [PATCH net-next 03/12] selftests: net: py: add test variants Jakub Kicinski
2025-11-17 20:58 ` [PATCH net-next 04/12] selftests: drv-net: xdp: use variants for qstat tests Jakub Kicinski
2025-11-17 20:58 ` [PATCH net-next 05/12] selftests: net: relocate gro and toeplitz tests to drivers/net Jakub Kicinski
2025-11-18 2:07 ` Willem de Bruijn
2025-11-17 20:58 ` [PATCH net-next 06/12] selftests: net: py: support ksft ready without wait Jakub Kicinski
2025-11-17 20:58 ` [PATCH net-next 07/12] selftests: net: py: read ip link info about remote dev Jakub Kicinski
2025-11-17 20:58 ` [PATCH net-next 08/12] netdevsim: pass packets thru GRO on Rx Jakub Kicinski
2025-11-18 2:07 ` Willem de Bruijn
2025-11-17 20:58 ` [PATCH net-next 09/12] selftests: drv-net: add a Python version of the GRO test Jakub Kicinski
2025-11-18 2:08 ` Willem de Bruijn
2025-11-17 20:58 ` [PATCH net-next 10/12] selftests: drv-net: hw: convert the Toeplitz test to Python Jakub Kicinski
2025-11-18 2:09 ` Willem de Bruijn
2025-11-17 20:58 ` [PATCH net-next 11/12] netdevsim: add loopback support Jakub Kicinski
2025-11-17 20:58 ` [PATCH net-next 12/12] selftests: net: remove old setup_* scripts Jakub Kicinski
2025-11-18 2:11 ` [PATCH net-next 00/12] selftests: drv-net: convert GRO and Toeplitz tests to work for drivers in NIPA Willem de Bruijn
2025-11-18 4:56 ` Jakub Kicinski [this message]
2025-11-18 14:13 ` Willem de Bruijn
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=20251117205609.4b0fa035@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=krakauer@google.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=willemdebruijn.kernel@gmail.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).