From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org
Subject: DTS WG Meeting Minutes - November 20, 2025
Date: Fri, 12 Dec 2025 14:52:06 -0500 [thread overview]
Message-ID: <CAJvnSUAb41bDcOf5q7H7cO0Hms+8JTG3FwEaAbGp3NkMem=f2g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
November 20, 2025
Attendees
* Patrick Robb
* Andrew Bailey
* Paul Szczepanek
Minutes
General Discussion
* RC3 has been released
* We are mostly done with DTS patches, but we can merge a couple more
such as the devtools docstrings check script and the formatting fix
patchseries
Patch discussions
* add test case docstring checks to format script
* We are permitted to add this for RC4
* Pydantic build fix was merged.
* doc: add test case docstring example to dts rst
* merged
* Virtio:
* merged
* Single_core_fwd_perf:
* merged
* RSS:
* merged
* QinQ:
* Merged
Bugzilla discussions
* Andrew and Patrick will update UNH DTS bugzilla tickets
Any other business
* Roadmap discussion (WIP):
* DTS API
* Resolve leftover parts
* 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
* Ensure the documentation for testing on a single host with a single
NIC is up to date
* Virtio testing support:
* Enable additional testing topologies and scenarios
* 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
* Flow Offload Testsuites:
* Add a new testsuite which creates a huge combination of patterns
and actions for rules, and tests them all.
* Next meeting is Dec 4, 2025
[-- Attachment #2: Type: text/html, Size: 1882 bytes --]
reply other threads:[~2025-12-12 19:53 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='CAJvnSUAb41bDcOf5q7H7cO0Hms+8JTG3FwEaAbGp3NkMem=f2g@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
/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).