From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: 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,
anubhavsinggh@google.com, richardbgobert@gmail.com,
linux-kselftest@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next v2 0/8] selftests: drv-net: gro: more test cases
Date: Thu, 02 Apr 2026 17:37:18 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.1b7e7cef1d1b6@gmail.com> (raw)
In-Reply-To: <20260402210000.1512696-1-kuba@kernel.org>
Jakub Kicinski wrote:
> Add a few more test cases for GRO.
>
> First 4 patches are unchanged from v1.
>
> Patches 5 and 6 are new. Willem pointed out that the defines are
> duplicated and all these imprecise defines have been annoying me
> for a while so I decided to clean them up.
>
> With the defines cleaned up and now more precise patch 7 (was 5)
> no longer has to play any games with the MTU for ip6ip6.
>
> The last patch now sends 3 segments as requested.
>
> v1: https://lore.kernel.org/20260401182625.372605-1-kuba@kernel.org
>
> Jakub Kicinski (8):
> selftests: drv-net: gro: add data burst test case
> selftests: drv-net: gro: add 1 byte payload test
> selftests: drv-net: gro: always wait for FIN in the capacity test
> selftests: drv-net: gro: prepare for ip6ip6 support
> selftests: drv-net: gro: remove TOTAL_HDR_LEN
> selftests: drv-net: gro: make large packet math more precise
> selftests: drv-net: gro: test ip6ip6
> selftests: drv-net: gro: add a test for bad IPv4 csum
>
> tools/testing/selftests/net/lib/gro.c | 207 +++++++++++++++------
> tools/testing/selftests/drivers/net/gro.py | 7 +-
> 2 files changed, 157 insertions(+), 57 deletions(-)
For the series:
Reviewed-by: Willem de Bruijn <willemb@google.com>
next prev parent reply other threads:[~2026-04-02 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 20:59 [PATCH net-next v2 0/8] selftests: drv-net: gro: more test cases Jakub Kicinski
2026-04-02 20:59 ` [PATCH net-next v2 1/8] selftests: drv-net: gro: add data burst test case Jakub Kicinski
2026-04-02 20:59 ` [PATCH net-next v2 2/8] selftests: drv-net: gro: add 1 byte payload test Jakub Kicinski
2026-04-02 20:59 ` [PATCH net-next v2 3/8] selftests: drv-net: gro: always wait for FIN in the capacity test Jakub Kicinski
2026-04-02 20:59 ` [PATCH net-next v2 4/8] selftests: drv-net: gro: prepare for ip6ip6 support Jakub Kicinski
2026-04-02 20:59 ` [PATCH net-next v2 5/8] selftests: drv-net: gro: remove TOTAL_HDR_LEN Jakub Kicinski
2026-04-02 20:59 ` [PATCH net-next v2 6/8] selftests: drv-net: gro: make large packet math more precise Jakub Kicinski
2026-04-02 20:59 ` [PATCH net-next v2 7/8] selftests: drv-net: gro: test ip6ip6 Jakub Kicinski
2026-04-02 21:00 ` [PATCH net-next v2 8/8] selftests: drv-net: gro: add a test for bad IPv4 csum Jakub Kicinski
2026-04-02 21:37 ` Willem de Bruijn [this message]
2026-04-03 23:10 ` [PATCH net-next v2 0/8] selftests: drv-net: gro: more test cases 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=willemdebruijn.kernel.1b7e7cef1d1b6@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=anubhavsinggh@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=richardbgobert@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.