From: Dean Marx <dmarx@iol.unh.edu>
To: probb@iol.unh.edu, npratte@iol.unh.edu, luca.vizzarro@arm.com,
yoan.picchi@foss.arm.com, Honnappa.Nagarahalli@arm.com,
paul.szczepanek@arm.com
Cc: dev@dpdk.org, Dean Marx <dmarx@iol.unh.edu>
Subject: [RFC PATCH 0/1] rte flow test suite
Date: Thu, 15 May 2025 12:38:08 -0400 [thread overview]
Message-ID: <20250515163809.184720-1-dmarx@iol.unh.edu> (raw)
This patch adds an initial Flow API test suite, which can
be expanded upon as Flow coverage becomes more widely supported.
Rather than creating one suite to test all possible Flow
rules, which would be statistically impossible due to the number
of possible combinations, this suite creates a framework for easily
implementing test cases in the future.
Dean Marx (1):
dts: add rte flow test suite
dts/tests/TestSuite_flow.py | 585 ++++++++++++++++++++++++++++++++++++
1 file changed, 585 insertions(+)
create mode 100644 dts/tests/TestSuite_flow.py
--
2.49.0
next reply other threads:[~2025-05-15 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 16:38 Dean Marx [this message]
2025-05-15 16:38 ` [RFC PATCH] dts: add " Dean Marx
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=20250515163809.184720-1-dmarx@iol.unh.edu \
--to=dmarx@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=luca.vizzarro@arm.com \
--cc=npratte@iol.unh.edu \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--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).