From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org, dts@dpdk.org,
"Luca Vizzarro" <Luca.Vizzarro@arm.com>,
"Dean Marx" <dmarx@iol.unh.edu>,
"Paul Szczepanek" <Paul.Szczepanek@arm.com>,
"Andrew Bailey" <abailey@iol.unh.edu>,
"Manit Mahajan" <mmahajan@iol.unh.edu>,
"Morten Brørup" <mb@smartsharesystems.com>
Subject: DTS WG Meeting Minutes - August 14, 2025
Date: Thu, 14 Aug 2025 17:38:04 -0400 [thread overview]
Message-ID: <CAJvnSUBN_X4cWYCZtmMRZgpgayCxqkCk9iDNc4Jkw+k3Ch-vQg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2785 bytes --]
#####################################################################
August 14, 2025
Attendees
* Patrick Robb
* Luca Vizzarro
* Paul Szczepanek
* Andrew Bailey
* Manit Mahajan
* Dean Marx
#####################################################################
Minutes
=====================================================================
General Discussion
* RFC deadline for 25.11 development is August 31.
=====================================================================
Patch discussions
* DPDKRuntimeEnvironment:
* Currently various methods in DPDKRuntimeEnvironment basically have a
switch for “SUT” or “TG” in various methods, though the
DPDKRuntimeEnvironment is only ever instantiated for the TG Node.
* So, proposal is to introduce an abstract class for
DPDKRuntimeEnvironment, with TG and SUT specific implementations of this
abstract class
* The main practical reason why we want to be able to instantiate a
variant of DPDKRuntimeEnvironment on the TG is in order to call
_prepare_devbind_script() so that the TG ports will bind to the correct
driver.
* Should we move the devbind responsibility to the topology class
* Could remove devbind_script_path from linux session
* and copy devbind to TG and SUT in the same way, meaning there is
one solution now for both nodes
* Add File Management:
* Desired testlogs output dir structure
* Testsuite logs and Testcase logs only include state information
* RSS:
* Patrick Robband Andrew Baileyto review this and test it on lab devices
* Rxtx_offload testsuite:
* Morten has drafted a required update to the testplan for mbuf fast
free. Patrick will send a new version in new DTS.
https://bugs.dpdk.org/show_bug.cgi?id=1769
* DTS API:
* In progress
* All of the files which are to be exposed to the testsuite surface will
be moved to a new “API” folder, and dts internals which should not be
imported to the testsuite will be located elsewhere.
* Splitting out some files, for instance for capabilities which users
will decorate their testsuites/cases with, the enums for those capabilities
are moved to the API dir, though the associated capability code will remain
outside of the API dir.
* Dean’s checksum testsuite doc updates were merged
=====================================================================
Bugzilla discussions
* Review bugzilla tickets:
*
https://bugs.dpdk.org/buglist.cgi?quicksearch=component%3Adts&list_id=9444
=====================================================================
Any other business
* VM setup - Virtio:
* Investigating different virtio workloads, topologies, and methods of
delivering a DPDK ready VM(s) to DTS
* Next meeting is Aug 28, 2025
[-- Attachment #2: Type: text/html, Size: 3101 bytes --]
reply other threads:[~2025-08-14 21:44 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=CAJvnSUBN_X4cWYCZtmMRZgpgayCxqkCk9iDNc4Jkw+k3Ch-vQg@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=dts@dpdk.org \
--cc=mb@smartsharesystems.com \
--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).