From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org
Subject: DTS WG Meeting Minutes - March 13, 2025
Date: Thu, 13 Mar 2025 19:32:34 -0400 [thread overview]
Message-ID: <CAJvnSUC9RQVCHTki5y01tRwnnBTV-jy+_TnGJrd89ocOq5ossg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2580 bytes --]
#####################################################################
March 13, 2025
Attendees
* Patrick Robb
* Paul Szczepanek
* Luca Vizzarro
#####################################################################
Minutes
General Discussion
* The DTS talk for Prague was accepted
* CFP writeup:
https://docs.google.com/document/d/1Bb-JDAGzn5BjEvypafG0azQqhVBxXuF8klFZ1xiUnmo/edit?usp=sharing
* Roadmap check in:
* TREX/TG support is pushed to next release, but Nick is working on this
currently
* VF support has a V5 but will not be merged with this release.
=====================================================================
Patch discussions
* Per testsuite configuration:
* 1 monolithic testsuite config file
* Merged
* VF port support patch and new questions:
* 1. Can we just destroy all VFs at DTS testrun setup?
* 2. Does creating the max number of vfs make the framework too slow?
* Patrick should look through the existing testplans and see what the
VF # requirements are (i.e. are they 1:1 with PFs in all cases)
* Perhaps the testsuites themselves should act as the source of truth
for number of VFs created
* TREX perf TG support:
* Some of the methods in the traffic_generator class are really for
capturing traffic generators - Nick is redefining the abstractions, has
stubbed out methods needed for perf TGs, and is implementing those in
trex.py
* Dean is refactoring some old testsuites:
* Port stats check: done (Patrick still needs to review)
* rx/tx_offload: Nearly done
* Ethertype:
* Luca will no longer pick this up (Nick can do this during 25.07)
* VLAN/TPID Filtering testcases for the ethertype testsuite cannot be
run on some devices in the UNH lab due to
https://bugs.dpdk.org/show_bug.cgi?id=1464
* UNH guys will work with the Intel and Broadcom PMD maintainers to
resolve these filtering issues, and then circle back to this testsuite for
25.07
* Packet capturing improvements:
* Current implementation provides arg for filtering. We have chosen to
not allow usage of packet filtering so far.
* Luca wants to modify the sniffing so that it will run during the
entire testrun instead of starting and stopping - packets can be pulled
from the sniffer as needed.
=====================================================================
Bugzilla discussions
*
=====================================================================
Any other business
* Roadmap status:
https://docs.google.com/document/d/1doTZOOpkv4D5P2w6K7fEJpa_CjzrlMl3mCeDBWtxnko/edit?tab=t.0
* Next meeting is Mar 13, 2025
[-- Attachment #2: Type: text/html, Size: 3071 bytes --]
reply other threads:[~2025-03-13 23:36 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=CAJvnSUC9RQVCHTki5y01tRwnnBTV-jy+_TnGJrd89ocOq5ossg@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).