From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org
Subject: DTS WG Meeting Minutes - May 22, 2025
Date: Sun, 1 Jun 2025 13:09:47 -0400 [thread overview]
Message-ID: <CAJvnSUDnag=QrgXriWEgj4a9X7BpTrBkMz-DH9nmr9=LM1=VXQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3569 bytes --]
#####################################################################
May 22, 2025
Attendees
* Patrick Robb
* Luca Vizzarro
* Paul Szczepanek
* Manit Mahajan
* Dean Marx
* Matthew McGovern
#####################################################################
Minutes
=====================================================================
General Discussion
* Nick Pratte from UNH-IOL is doing an internship outside IOL this Summer,
so he will not be working on DTS as much as expected
* He still wants to submit some testsuites this Summer, but all his
framework side work (like perf tg (trex) support) will go to Patrick or Dean
* He may be back to working on DTS more regularly at the end of the
Summer that is TBD
* CI Lab items:
* We’re still debugging some of the failures that we saw on the cx5
before DPDK Summit, which took that testing offline in our public reporting
system
* Dean is adding some new NICs to the public testing
* Broadcom 25g
* Broadcom 100g (p2100g)
=====================================================================
Patch discussions
* Rte_flow: https://patchwork.dpdk.org/project/dpdk/list/?series=35269
* Dean has updated the flow testsuite, adding a flow validate step
* If flow validate fails, skip the testsuite
* If flow validate passes, then flow create fails, fail the testsuite
* If flow validate passes, flow create passes, then run the testsuite
and validate the flow behavior (pass or fail based on testsuite assert)
* Dean added a verify_skip method to the testsuite class used for
skipping testsuites at runtime based on some condition
* Per test suite config docs:
https://patchwork.dpdk.org/project/dpdk/list/?series=35240
* Doc update towards explaining how to leverage the per test suite config
* Perf tg support:
https://patchwork.dpdk.org/project/dpdk/list/?series=35239
* Patrick is picking up this series
* UNH people will ensure that the forwarding test metrics align with the
results we get from legacy DTS, which is considered stable
* The legacy framework single core forwarding test had some effort done
towards supporting different traffic mixes/profiles, and we should examine
this for the new testsuite, but the MVP will feature basically a uniform
set of packets
* L4 packet matching:
https://patchwork.dpdk.org/project/dpdk/list/?series=3522
* Luca provided a few nits
* Nits are resolved, so Patrick can test and merge
* Improved port handling:
https://patchwork.dpdk.org/project/dpdk/patch/20250506131657.1576152-1-luca.vizzarro@arm.com/
* Patrick needs to review ASAP
* Packet capture testsuite:
https://patchwork.dpdk.org/project/dpdk/list/?series=35163
* UNH guys need to provide a review and test on our hardware
* Tmp dir dpdk tree dir:
https://patchwork.dpdk.org/project/dpdk/list/?series=35049
* UNH guys need to provide a review
* Patrick needs to resolve a docs error from the stats testsuite
=====================================================================
Bugzilla discussions
* None
=====================================================================
Any other business
* DPDK-Pktgen
* Patrick should share the pktgen notes and code example the CESNET guys
shared at a future meeting
* Cloud testing
* Matthew is setting up an environment on Azure to experiment with DTS.
* Group looked at roadmap status DTS 25.07 Roadmap
* Luca will be gone for 3 weeks, and will be back in the 2nd half of June
* Next meeting is Jun 5, 2025
[-- Attachment #2: Type: text/html, Size: 4285 bytes --]
reply other threads:[~2025-06-01 17: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='CAJvnSUDnag=QrgXriWEgj4a9X7BpTrBkMz-DH9nmr9=LM1=VXQ@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).