From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org, Luca Vizzarro <Luca.Vizzarro@arm.com>,
Paul Szczepanek <Paul.Szczepanek@arm.com>,
Dean Marx <dmarx@iol.unh.edu>,
Manit Mahajan <mmahajan@iol.unh.edu>,
Andrew Bailey <abailey@iol.unh.edu>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: DTS 25.11 Roadmap
Date: Wed, 30 Jul 2025 20:07:51 -0400 [thread overview]
Message-ID: <CAJvnSUB2scYCkV4BKFyxHVpPLFmhLYVb20tV0LFDeUHLWfVW+Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
Hello,
The DTS group has met and agreed on the top level goals for 25.11 DTS
development.
DTS Roadmap:
* DTS API
* Provide a single point of entry into the framework for all test
suites, allowing stable usage across releases and user friendly
discoverability of dts functionality
* Packet Forwarding Performance Tests
* Cryptodev testing
* (framework): Adding a shell class for the dpdk-crypto-perf
application
* (testsuites) : Encrypt/decrypt workloads with the various supported
algorithms on DPDK NICs.
* Can be implemented as a set of functional tests or (pending
community discussion) can support crypto performance baselines
* Testing with single NIC with the 2 interfaces connected in a loopback
* This appears to be working currently, but need to be documented
better for users
* Virtio testing support:
* Add support for DTS spinning up a QEMU VM with a virtio device
* Implement various testing scenarios for virtio interfaces on a VM
* Additional functional ethdev testsuites:
* Ethertype Testsuite
* QinQ Testsuite
* RSS Testsuite
* Rx/Tx Offload
* And additional suites as detailed on Bugzilla where possible
* File manager:
* Add a dedicated file manager to handle passing files and artifacts
[-- Attachment #2: Type: text/html, Size: 1515 bytes --]
reply other threads:[~2025-07-31 0:14 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=CAJvnSUB2scYCkV4BKFyxHVpPLFmhLYVb20tV0LFDeUHLWfVW+Q@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=abailey@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=mmahajan@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).