From: jspewock@iol.unh.edu
To: npratte@iol.unh.edu, juraj.linkes@pantheon.tech,
Honnappa.Nagarahalli@arm.com, wathsala.vithanage@arm.com,
alex.chapman@arm.com, probb@iol.unh.edu, paul.szczepanek@arm.com,
yoan.picchi@foss.arm.com, Luca.Vizzarro@arm.com,
thomas@monjalon.net
Cc: dev@dpdk.org, Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [PATCH v2 0/2] dts: pf_smoke port
Date: Fri, 6 Sep 2024 12:51:49 -0400 [thread overview]
Message-ID: <20240906165151.14668-1-jspewock@iol.unh.edu> (raw)
In-Reply-To: <20240806185631.335737-1-jspewock@iol.unh.edu>
From: Jeremy Spewock <jspewock@iol.unh.edu>
v2:
* update dependencies and how the test suite uses them
* use a unique src MAC on packets to find them in verbose output
rather than checksums since using checksums isn't supported on all
NICs
* formatting fixes and doc-string updates
Jeremy Spewock (2):
dts: add ability to modify number of queues on a port to testpmd
dts: add pf smoke testing suite
dts/framework/config/conf_yaml_schema.json | 3 +-
dts/framework/remote_session/testpmd_shell.py | 36 ++++++
dts/tests/TestSuite_pf_smoke_tests.py | 121 ++++++++++++++++++
3 files changed, 159 insertions(+), 1 deletion(-)
create mode 100644 dts/tests/TestSuite_pf_smoke_tests.py
--
2.46.0
next prev parent reply other threads:[~2024-09-06 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 18:56 [RFC PATCH v1 0/3] " jspewock
2024-08-06 18:56 ` [RFC PATCH v1 1/3] dts: add ability to modify number of queues on a port to testpmd jspewock
2024-08-06 18:56 ` [RFC PATCH v1 2/3] dts: add pf smoke testing suite jspewock
2024-08-06 18:56 ` [RFC PATCH v1 3/3] dts: added pf_smoke_tests to yaml schema jspewock
2024-09-06 16:51 ` jspewock [this message]
2024-09-06 16:51 ` [PATCH v2 1/2] dts: add ability to modify number of queues on a port to testpmd jspewock
2024-09-06 16:51 ` [PATCH v2 2/2] dts: add pf smoke testing suite 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=20240906165151.14668-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).