From: Nicholas Pratte <npratte@iol.unh.edu>
To: ian.stokes@intel.com, yoan.picchi@foss.arm.com,
probb@iol.unh.edu, paul.szczepanek@arm.com,
Honnappa.Nagarahalli@arm.com, thomas@monjalon.net,
luca.vizzarro@arm.com, thomas.wilks@arm.com, dmarx@iol.unh.edu,
stephen@networkplumber.org
Cc: dev@dpdk.org, Nicholas Pratte <npratte@iol.unh.edu>
Subject: [RFC Patch v1 0/5] Add TREX Traffic Generator to DTS Framework
Date: Wed, 23 Apr 2025 15:40:06 -0400 [thread overview]
Message-ID: <20250423194011.1447679-1-npratte@iol.unh.edu> (raw)
Included in a semi-complete, RFC implementation for a would-be
implementation of the TREX traffic generator, in addition to a
mock implementation of a single core performance test suite,
leveraging newly added performance test API functionality.
Code is incomplete with a handful of typing issues, but does execute
without errors on my system.
Nicholas Pratte (5):
dts: rework config module to support perf TGs
dts: rework traffic generator inheritance structure.
dts: add asychronous support to ssh sessions.
dts: add trex traffic generator to dts framework
dts: add performance test functions to test suite api
dts/{ => configurations}/nodes.example.yaml | 0
.../test_run.example.yaml | 8 +-
.../tests_config.example.yaml | 0
.../trex_configs/intel_40g.yaml | 18 ++
dts/framework/config/test_run.py | 20 +-
dts/framework/context.py | 11 +-
dts/framework/remote_session/ssh_session.py | 17 ++
dts/framework/settings.py | 6 +-
dts/framework/test_run.py | 28 +-
dts/framework/test_suite.py | 33 +-
.../traffic_generator/__init__.py | 22 +-
.../capturing_traffic_generator.py | 34 +++
.../performance_traffic_generator.py | 62 ++++
.../traffic_generator/traffic_generator.py | 43 +--
.../testbed_model/traffic_generator/trex.py | 287 ++++++++++++++++++
dts/tests/TestSuite_single_core_perf.py | 24 ++
16 files changed, 550 insertions(+), 63 deletions(-)
rename dts/{ => configurations}/nodes.example.yaml (100%)
rename dts/{ => configurations}/test_run.example.yaml (82%)
rename dts/{ => configurations}/tests_config.example.yaml (100%)
create mode 100644 dts/configurations/trex_configs/intel_40g.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_perf.py
--
2.47.1
next reply other threads:[~2025-04-23 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 19:40 Nicholas Pratte [this message]
2025-04-23 19:40 ` [RFC Patch v1 1/5] dts: rework config module to support perf TGs Nicholas Pratte
2025-04-23 19:40 ` [RFC Patch v1 2/5] dts: rework traffic generator inheritance structure Nicholas Pratte
2025-04-23 19:40 ` [RFC Patch v1 3/5] dts: add asychronous support to ssh sessions Nicholas Pratte
2025-04-23 19:40 ` [RFC Patch v1 4/5] dts: add trex traffic generator to dts framework Nicholas Pratte
2025-04-23 19:40 ` [RFC Patch v1 5/5] dts: add performance test functions to test suite api Nicholas Pratte
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=20250423194011.1447679-1-npratte@iol.unh.edu \
--to=npratte@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=ian.stokes@intel.com \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=stephen@networkplumber.org \
--cc=thomas.wilks@arm.com \
--cc=thomas@monjalon.net \
--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).