From: jspewock@iol.unh.edu
To: Honnappa.Nagarahalli@arm.com, probb@iol.unh.edu,
paul.szczepanek@arm.com, juraj.linkes@pantheon.tech,
yoan.picchi@foss.arm.com, npratte@iol.unh.edu,
wathsala.vithanage@arm.com, Luca.Vizzarro@arm.com,
alex.chapman@arm.com, thomas@monjalon.net
Cc: dev@dpdk.org, Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [RFC PATCH v1 0/5] dts: port over Rx/Tx offload suite
Date: Fri, 30 Aug 2024 20:00:08 -0400 [thread overview]
Message-ID: <20240831000058.23009-1-jspewock@iol.unh.edu> (raw)
From: Jeremy Spewock <jspewock@iol.unh.edu>
This series ports over the functionality of the Rx/Tx offloading test
suite from Old DTS. I marked this suite as an RFC since there are still
some errors that I need to fix from the formatting script, but I felt
that the commits were in a place where they could be viewed to
understand the idea of what I was working on.
There are a lot of dependencies for this series, I listed them below in
the order that I applied them.
depends-on: patch-142691 (“dts:add send_packets to test suites and
rework packet addressing”)
depends-on: series-32799 (“dts: add test skipping based on
capabilities”)
depends-on: patch-143033 (“dts: add text parser for testpmd verbose
output”)
depends-on: patch-143385 (“dts: add VLAN methods to testpmd shell”)
depends-on: patch-143113 ("dts: add flow rule dataclass to testpmd
shell")
Jeremy Spewock (5):
dts: add TX offload capabilities
dts: add a distinction between port and queue offload capabilities
dts: add offload configuration querying to testpmd
dts: add methods for configuring offloads on a device in testpmd
dts: add test suite for RX and TX offloads
dts/framework/config/conf_yaml_schema.json | 3 +-
dts/framework/remote_session/testpmd_shell.py | 908 +++++++++++++++---
dts/tests/TestSuite_pmd_buffer_scatter.py | 2 +-
dts/tests/TestSuite_rxtx_offload.py | 622 ++++++++++++
4 files changed, 1414 insertions(+), 121 deletions(-)
create mode 100644 dts/tests/TestSuite_rxtx_offload.py
--
2.46.0
next reply other threads:[~2024-08-31 0:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 0:00 jspewock [this message]
2024-08-31 0:00 ` [RFC PATCH v1 1/5] dts: add TX offload capabilities jspewock
2024-08-31 0:00 ` [RFC PATCH v1 2/5] dts: add a distinction between port and queue " jspewock
2024-08-31 0:00 ` [RFC PATCH v1 3/5] dts: add offload configuration querying to testpmd jspewock
2024-08-31 0:00 ` [RFC PATCH v1 4/5] dts: add methods for configuring offloads on a device in testpmd jspewock
2024-08-31 0:00 ` [RFC PATCH v1 5/5] dts: add test suite for RX and TX offloads jspewock
2024-09-03 19:46 ` [PATCH v2 0/5] dts: port over Rx/Tx offload suite jspewock
2024-09-03 19:46 ` [PATCH v2 1/5] dts: add TX offload capabilities jspewock
2024-09-03 19:46 ` [PATCH v2 2/5] dts: add a distinction between port and queue " jspewock
2024-09-03 19:46 ` [PATCH v2 3/5] dts: add offload configuration querying to testpmd jspewock
2024-09-03 19:46 ` [PATCH v2 4/5] dts: add methods for configuring offloads on a device in testpmd jspewock
2024-09-03 19:46 ` [PATCH v2 5/5] dts: add test suite for RX and TX offloads jspewock
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=20240831000058.23009-1-jspewock@iol.unh.edu \
--to=jspewock@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Luca.Vizzarro@arm.com \
--cc=alex.chapman@arm.com \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=npratte@iol.unh.edu \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=wathsala.vithanage@arm.com \
--cc=yoan.picchi@foss.arm.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).