From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: Dean Marx <dmarx@iol.unh.edu>,
Andrew Bailey <abailey@iol.unh.edu>,
Lincoln Lavoie <lylavoie@iol.unh.edu>,
Paul Szczepanek <Paul.Szczepanek@arm.com>,
Luca Vizzarro <Luca.Vizzarro@arm.com>,
ci@dpdk.org
Subject: 26.03 DTS Roadmap
Date: Fri, 12 Dec 2025 15:09:37 -0500 [thread overview]
Message-ID: <CAJvnSUB6w6ipyyTuP6fGXiO+qg-pN0+S2KVQDAXNC1qyfVXd1A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]
Hello,
The DTS group has met and agreed on the development goals for the 26.03
DPDK release.
Roadmap:
* DTS API
* Remove all existing framework imports and replace with imports from the
DTS API
* Cryptodev testing
* Adding a new cryptodev package to the DTS API for handling
dpdk-crypto-perf app arguments
* (testsuites) : Encrypt/decrypt workloads with the various supported
algorithms on DPDK crypto cards.
* Supporting DTS testruns on 1 physical host:
* Provide additional documentation and framework updates for testing on a
single host with a single NIC
* Virtio testing support:
* Enable additional testing topologies and scenarios (e.g. add a PvvP test
which is structured similar to the existing PvP test)
* Flow Offload Testsuites:
* Add a new testsuite which categorizes network protocols and their
respective valid field values by OSI layer, and creates all unique
combinations of these as flow rules. This should create “comprehensive”
coverage of flow rules where previously we just had the minimal set of flow
offload rules tested.
* Asynchronous API testing
* Additional functional ethdev testsuites:
* Ethertype Testsuite
* QinQ testing: Extend this testsuite to validate that IDs are being stored
in the correct TCI / OUTER_TCI via testpmd verbose logs
* Add support for producing code coverage reports from a DTS testrun (so,
show how much of the DPDK code the testsuites are touching)
* Misc QoL improvements (e.g. update testsuite names for clarity)
[-- Attachment #2: Type: text/html, Size: 8796 bytes --]
reply other threads:[~2025-12-12 20:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJvnSUB6w6ipyyTuP6fGXiO+qg-pN0+S2KVQDAXNC1qyfVXd1A@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=abailey@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=lylavoie@iol.unh.edu \
/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).