public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
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, shuah@kernel.org,
	linux-kselftest@vger.kernel.org, sdf@fomichev.me,
	willemb@google.com, petrm@nvidia.com,
	Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next v3 0/6] selftests: drv-net: gro: enable HW GRO and LRO testing
Date: Mon, 12 Jan 2026 16:07:34 -0800	[thread overview]
Message-ID: <20260113000740.255360-1-kuba@kernel.org> (raw)

Add support for running our existing GRO test against HW GRO
and LRO implementation. The first 3 patches are just ksft lib
nice-to-haves, and patch 4 cleans up the existing gro Python.

Patches 5 and 6 are of most practical interest. The support
reconfiguring the NIC to disable SW GRO and enable HW GRO and LRO.
Additionally last patch breaks up the existing GRO cases to
track HW compliance at finer granularity.

v3:
 - patch 4 - s/tso/tcp-segmentation-offload/ for ethtool feature names
 - patch 5 - explicitly skip LRO on netdevsim, it lies about support
 - patch 6 - add enum for the flush_id test configs
v2: https://lore.kernel.org/20260110005121.3561437-1-kuba@kernel.org
 - fix restoring all features
 - apply the generic XDP hack selectively (print a msg when it happens)
 - a lot of small tweaks and 4 extra patches
v1: https://lore.kernel.org/20251128005242.2604732-1-kuba@kernel.org

Jakub Kicinski (6):
  selftests: net: py: teach ksft_pr() multi-line safety
  selftests: net: py: teach cmd() how to print itself
  selftests: drv-net: gro: use cmd print
  selftests: drv-net: gro: improve feature config
  selftests: drv-net: gro: run the test against HW GRO and LRO
  selftests: drv-net: gro: break out all individual test cases

 tools/testing/selftests/drivers/net/gro.c     | 433 ++++++++++--------
 tools/testing/selftests/drivers/net/gro.py    | 163 ++++++-
 .../selftests/drivers/net/lib/py/env.py       |   7 +-
 tools/testing/selftests/net/lib/py/ksft.py    |  29 +-
 tools/testing/selftests/net/lib/py/utils.py   |  23 +
 5 files changed, 439 insertions(+), 216 deletions(-)

-- 
2.52.0


             reply	other threads:[~2026-01-13  0:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13  0:07 Jakub Kicinski [this message]
2026-01-13  0:07 ` [PATCH net-next v3 1/6] selftests: net: py: teach ksft_pr() multi-line safety Jakub Kicinski
2026-01-13  0:07 ` [PATCH net-next v3 2/6] selftests: net: py: teach cmd() how to print itself Jakub Kicinski
2026-01-13  0:07 ` [PATCH net-next v3 3/6] selftests: drv-net: gro: use cmd print Jakub Kicinski
2026-01-13  0:07 ` [PATCH net-next v3 4/6] selftests: drv-net: gro: improve feature config Jakub Kicinski
2026-01-13  0:07 ` [PATCH net-next v3 5/6] selftests: drv-net: gro: run the test against HW GRO and LRO Jakub Kicinski
2026-01-13  0:07 ` [PATCH net-next v3 6/6] selftests: drv-net: gro: break out all individual test cases Jakub Kicinski
2026-01-14  2:40 ` [PATCH net-next v3 0/6] selftests: drv-net: gro: enable HW GRO and LRO testing patchwork-bot+netdevbpf

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=20260113000740.255360-1-kuba@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=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=sdf@fomichev.me \
    --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