From: Patrick Robb <probb@iol.unh.edu>
To: luca.vizzarro@arm.com
Cc: dev@dpdk.org, dmarx@iol.unh.edu, abailey@iol.unh.edu,
Paul.Szczepanek@arm.com, Patrick Robb <probb@iol.unh.edu>
Subject: [PATCH v7 0/3] Add TREX Traffic Generator to DTS Framework
Date: Wed, 12 Nov 2025 20:26:22 -0500 [thread overview]
Message-ID: <20251113012625.1058035-1-probb@iol.unh.edu> (raw)
This series adds support for performance traffic generators, and
includes an implementation for using the TREX traffic generator for
performance testing. It also includes a new testsuite which measures the
single core forwarding performance of a SUT in millions of packets per
second.
v7 changes:
- Added missing spdx tag
- Per DTS meeting conversation, add 16B descriptor tag to Intel builds
to allow for the highest throughput on performance testing
Nicholas Pratte (3):
dts: rework traffic generator inheritance structure
dts: add trex traffic generator to dts framework
dts: add performance test functions and support
...sts.TestSuite_single_core_forward_perf.rst | 8 +
doc/guides/tools/dts.rst | 55 +++-
dts/api/packet.py | 39 ++-
dts/api/test.py | 32 +++
dts/{ => configurations}/nodes.example.yaml | 0
.../test_run.example.yaml | 6 +-
dts/configurations/tests_config.example.yaml | 17 ++
dts/framework/config/test_run.py | 22 +-
dts/framework/context.py | 5 +-
dts/framework/remote_session/blocking_app.py | 12 +-
dts/framework/remote_session/dpdk.py | 15 +-
.../remote_session/interactive_shell.py | 8 +-
dts/framework/settings.py | 12 +-
dts/framework/test_run.py | 52 +++-
.../traffic_generator/__init__.py | 13 +-
.../capturing_traffic_generator.py | 34 +++
.../performance_traffic_generator.py | 59 ++++
.../testbed_model/traffic_generator/scapy.py | 14 +-
.../traffic_generator/traffic_generator.py | 44 +--
.../testbed_model/traffic_generator/trex.py | 259 ++++++++++++++++++
.../TestSuite_single_core_forward_perf.py | 149 ++++++++++
dts/tests_config.example.yaml | 5 -
22 files changed, 778 insertions(+), 82 deletions(-)
create mode 100644 doc/api/dts/tests.TestSuite_single_core_forward_perf.rst
rename dts/{ => configurations}/nodes.example.yaml (100%)
rename dts/{ => configurations}/test_run.example.yaml (88%)
create mode 100644 dts/configurations/tests_config.example.yaml
create mode 100644 dts/framework/testbed_model/traffic_generator/performance_traffic_generator.py
create mode 100644 dts/framework/testbed_model/traffic_generator/trex.py
create mode 100644 dts/tests/TestSuite_single_core_forward_perf.py
delete mode 100644 dts/tests_config.example.yaml
--
2.49.0
next reply other threads:[~2025-11-13 1:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 1:26 Patrick Robb [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-05 22:36 [PATCH v6 " Patrick Robb
2025-11-13 1:27 ` [PATCH v7 " Patrick Robb
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=20251113012625.1058035-1-probb@iol.unh.edu \
--to=probb@iol.unh.edu \
--cc=Paul.Szczepanek@arm.com \
--cc=abailey@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=luca.vizzarro@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).