DTS WG Meeting Minutes - January 29, 2026

[Patrick Robb]

January 29, 2026

Attendees
* Patrick Robb
* Luca Vizzarro
* Matthew Labrecque

Minutes

General Discussion
* The release candidate 1 (RC1) date is 9 February 2026

Patch discussions
* Cryptodev testing:
   * https://patchwork.dpdk.org/project/dpdk/list/?series=37138
   * Andrew working on v2
      * User to provide the dpdk-crypto-perf’s –devtype parameter via
the tests_config.yaml
      * Extending test coverage to include:
         * Additional virtual devices
         * A greater matrix of ciphers, authentication algorithms, and devices
      * What about the vdev value which is set in the DTS config test_run.yaml?
         * What is does is it adds a vdev argument to EAL arguments in DTS
         * We would have a need for this if we needed to parameterize
any vdev values within testsuitse or broadly run DPDK apps (testpmd
etc.) with a particular vdev, but this is not a need/scenario for
testing we are aware of.
            * So, Andrew/Patrick to check in on this and most likely
remove the vdev value from test_run.yaml
* Flow offload testing:
   * Patrick reviewed, Dean to work on a new version
   * Noting that the new flow offload test takes about 15 minutes to
run due to the 1000+ rules to validate.
      * Patrick is asking for more protocol fieldparameters and
protocols to be added to the next version, so all else being equal
this will increase even further
      * Is this an issue? Is there a need to introduce a “fast tests”
option to DTS where a user sets DTS to only run the quick tests
(basically everything other than flow offload and RSS tests)
         * https://bugs.dpdk.org/show_bug.cgi?id=1872
      * Should we maintain the “minimal-rule-set” testsuite (what is
on mainline right now) and add in this “comprehensive-rule-set”
testsuite that has a long execution time as separate testsuites, or
remove the minimal testsuite entirely.
      * What happens when the confidence check (send a non-matching
packet) “fails?” Skipped testcase? Anything else?
      * What about asynchronous API? Is there a goal to add some
support for this in 26.07? Should we get started now?
* Can be merged:
   * https://patchwork.dpdk.org/project/dpdk/list/?series=37136
   * https://patchwork.dpdk.org/project/dpdk/list/?series=36907
   * (requires final review)
https://patchwork.dpdk.org/project/dpdk/list/?series=36896

Bugzilla discussions
* N/A

Any other business
* Roadmap review: Looks pretty good, there are some items which are
“small” and we can toggle to soon when the big testsuites are merged
to next-dts
   * There are also some medium sized bullets which we need to discuss
more imminently:
      * 1. Add support for producing code coverage reports from a DTS
testrun (so, show how much of the DPDK code the testsuites are
touching)
         * Raise this at the CI meeting next Thursday
      * 2. asynchronous API testing in flow offload testsuite(s)
* Next meeting is Feb 12, 2026