<div dir="ltr">#####################################################################<br>March 20, 2025<br>Attendees<br>1. Patrick Robb<br>2. Paul Szczepanek<br>3. Luca Vizzarro<br>4. Cody Cheng<br>5. Aaron Conole<br>6. Matthew McGovern<br>7. Dean Marx<br><br>#####################################################################<br>Minutes<br><br>=====================================================================<br>General Announcements<br>* RC3 has been released<br> * Next-dts has been pulled to main<br> * DPDK 25.03 will be released in a few days<br>* Pw-ci project: Aaron is syncing his internal repo to the upstream<br> * Adds recheck support, and other reporting scripts<br> <br>=====================================================================<br>CI Status<br><br>---------------------------------------------------------------------<br>UNH-IOL Community Lab<br>* New DTS:<br> * Running a broader set of “new DTS” tests on Intel XL710 and CX5 NICs now:<br> * Unified Packet<br> * Promiscuous Support<br> * PMD Buffer Scatter<br> * Dynamic Queue Config<br> * Dynamic Config<br> * MAC Filter<br>* Cody has begun work on setting up a VM which will be locked to the minimum kernel version supported by DPDK - this system will do build tests.<br> * According to DPDK docs, that is kernel version 4.19, but it links to a kernel mirror site which indicates a newer minimum supported kernel - Cody is going to reach out on the mailing list for clarification<br>* The patch adding patch series dependency support to DPDK Patchwork has been accepted: <a href="https://patchwork.ozlabs.org/project/patchwork/list/?series=442332&state=*">https://patchwork.ozlabs.org/project/patchwork/list/?series=442332&state=*</a><br> * We will need to work with Ali after the next patchwork release to get the DPDK Patchwork instance updated to the latest release<br>* Build failure emails:<br> * Build failure emails were not including the Meson and Ninja logs due to a bad HTTP server reconfiguration we had deployed. This issue is now resolved and we see the most recent build failure comes with the relevant logs.<br> <br> ---------------------------------------------------------------------<br>Intel Lab<br>* None<br><br>---------------------------------------------------------------------<br>Github Actions<br>* Cirrus CI: No one is working on the FreeBSD support, so unit tests still fail, and this decreases the value added by Cirrus CI<br>* Working on an update which will associate a run number with a recheck request<br><br>---------------------------------------------------------------------<br>AWS<br>* They are working on their test-report email templating script<br>* There was some conversation at the joint Governing Board and Tech Board meeting about platforms AWS will run from and their testing goals:<br> * Platforms: includes x86 and ARM Graviton based systems<br> * Goals: Will setup a CI lab which will target build and unit tests first, then target some functional and performance testing with DTS.<br> <br>---------------------------------------------------------------------<br>Loongarch Lab<br>* None<br><br><br>=====================================================================<br>DTS Improvements & Test Development<br>* DTS Packet Sniffer update:<br> * Breaks the sniffer out into a new class which is run separately from Scapy TG class<br> * It can start/stop and collect packets whenever directed to do so via the TestSuite API<br> * Async sniffer will run throughout the entire testrun instead of starting and stopping.<br> * Adds a facility to trigger a stop condition for the sniffer (like stop as soon as you sniff packet X)<br> * This is not exposed via the TestSuite API currently<br> * Currently Sniffer is integrated into the scapy class, but there is no particular reason for this - it could reasonably be moved to the TestSuite and exposed <br>* DTS Roadmap 25.07<br> * Rte_flow<br> * Performance TG and forwarding tests<br> * Improved documentation<br> * TestSuite API<br> * Paul is interested in moving from the TestSuite class as API to a “DPDK” API for DTS testsuites. This would involved committing to a stable API. We would be able to change framework internals without breaking testsuites.<br> * The biggest advantage would be discoverability for a new test writer who has not seen DTS before<br> * Cloud environment support for DTS<br> * VF Support<br>* VF support:<br> * No movement on the VF support series<br>* TestSuite Development:<br> * Dean has submitted updates for unified packet testsuite and checksum offload testsuite which switches from matching packets on mac dst address to relying on l4 port number.<br>* Testrun duration:<br> * Perhaps we should profile the testsuites into different buckets and add config options for running certain groups of tests<br> * By keeping the sniffer process on the entire time, we will cut out a lot of time waiting for sniffer to start and stop<br> * One option would be to keep testpmd open through the entire testrun, and just reset it for each testsuite without restarting it and going through EAL bring up (takes a few seconds). On the other hand, the appeal of restarting testpmd completely is we know it is totally reset.<br> * Possible keep 1 testpmd shell per testsuite, and that testsuite is responsible for cleaning up the shell properly in between testcases<br><br>=====================================================================<br>Any other business<br>* Azure: We got more details from Matthew about the DPDK testing goals for Microsoft Azure<br> * Environments: They can run testing on cloud instances based on Intel x86, AMD x86, and ARM systems<br> * Mellanox NICs are available to some cloud instances on Azure<br> * They would like to run functional and performance tests and products reports for those for <a href="http://dpdk.org">dpdk.org</a><br> * Performance tests: will be simple single and multi-queue testpmd MPPS forwarding tests<br> * They cannot commit to a report cadence right now, but discussed the idea of releasing a report per DPDK release, as well as rolling reports on main<br>* Next Meeting Apr 3, 2025<br></div>