From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org
Subject: DTS WG Meeting Minutes - September 25, 2025
Date: Thu, 2 Oct 2025 15:57:57 -0400 [thread overview]
Message-ID: <CAJvnSUD=XxjmYP7rXwZgPNijvoeS3X9_YJopJxgsf9Lad5rggw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1942 bytes --]
####################################################################
September 25, 2025
Attendees
* Patrick Robb
* Luca Vizzarro
* Andrew Bailey
* Paul Szczepanek
* Indira K
####################################################################
Minutes
=====================================================================
General Discussion
* DTS Videos links:
* How to set up and run DTS:
https://www.youtube.com/watch?v=vxii8pboNAI&pp=ygUHdW5oIGlvbA%3D%3D
* How to write a testsuite:
https://www.youtube.com/watch?v=3w9XrYtTvqE&pp=ygUHdW5oIGlvbA%3D%3D
=====================================================================
Patch discussions
* Recently merged:
* DTS API
* Testsuite Docstrings update
* TG Driver Bind
* RSS:
* Dean is currently testing/reviewing
* Mbuf fast release testcase / tx_offload:
* Framework changes look to be almost done.
* Virtio:
* V1 is sent
* Patrick Robb to do a test/review
* Single_core_fwd_perf:
* Need to rebase on main before submitting the next version because of
the DTS API patch
* Need to ensure the docstrings are compliant with the current
testsuites docstring structure
* Move testsuite methods to API modules
* Patrick to do a review
=====================================================================
Bugzilla discussions
* None
=====================================================================
Any other business
* Roadmap status review:
*
https://docs.google.com/document/d/1doTZOOpkv4D5P2w6K7fEJpa_CjzrlMl3mCeDBWtxnko/edit?tab=t.0
* Paul notes for next release we should implement an API freeze for DTS
* Next meeting is Oct 9, 2025
* We are still inheriting from TestSuite, which is an internal framework
object which should not be imported. Maybe the most reasonable thing would
be for the API to have a class/interface
* Add a TestSuite class to API which inherits from protocol, with set up
test suite, set up test case methods etc.
[-- Attachment #2: Type: text/html, Size: 2464 bytes --]
reply other threads:[~2025-10-02 19:58 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='CAJvnSUD=XxjmYP7rXwZgPNijvoeS3X9_YJopJxgsf9Lad5rggw@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).