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,
willemdebruijn.kernel@gmail.com, petrm@nvidia.com,
stfomichev@gmail.com, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next v2 0/3] selftests: drv-net: add a simple TSO test
Date: Fri, 14 Feb 2025 15:46:28 -0800 [thread overview]
Message-ID: <20250214234631.2308900-1-kuba@kernel.org> (raw)
Add a simple test for exercising TSO over tunnels.
v2:
- [patch 1] check for IP being on multiple ifcs
- [patch 3] lower max noise
- [patch 3] mention header overhead in the comment
- [patch 3] fix the basic v4 TSO feature name
- [patch 3] also run a stream with just GSO partial for tunnels
v1: https://lore.kernel.org/20250213003454.1333711-1-kuba@kernel.org
Jakub Kicinski (3):
selftests: drv-net: resolve remote interface name
selftests: drv-net: get detailed interface info
selftests: drv-net: add a simple TSO test
.../testing/selftests/drivers/net/hw/Makefile | 1 +
tools/testing/selftests/drivers/net/hw/tso.py | 234 ++++++++++++++++++
.../selftests/drivers/net/lib/py/env.py | 19 +-
3 files changed, 252 insertions(+), 2 deletions(-)
create mode 100755 tools/testing/selftests/drivers/net/hw/tso.py
--
2.48.1
next reply other threads:[~2025-02-14 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 23:46 Jakub Kicinski [this message]
2025-02-14 23:46 ` [PATCH net-next v2 1/3] selftests: drv-net: resolve remote interface name Jakub Kicinski
2025-02-15 14:50 ` Willem de Bruijn
2025-02-17 11:42 ` Petr Machata
2025-02-14 23:46 ` [PATCH net-next v2 2/3] selftests: drv-net: get detailed interface info Jakub Kicinski
2025-02-15 14:50 ` Willem de Bruijn
2025-02-14 23:46 ` [PATCH net-next v2 3/3] selftests: drv-net: add a simple TSO test Jakub Kicinski
2025-02-15 14:49 ` Willem de Bruijn
2025-02-15 16:31 ` Jakub Kicinski
2025-02-15 14:50 ` 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=20250214234631.2308900-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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=stfomichev@gmail.com \
--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).