From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org
Subject: DTS WG Meeting Minutes - October 9, 2025
Date: Mon, 3 Nov 2025 22:34:14 -0500 [thread overview]
Message-ID: <CAJvnSUCgBnw=wXi-1ugP_RYZYMBC2xY2VGBBxv0_WEuekiLYAQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]
####################################################################
October 9, 2025
Attendees
* Patrick Robb
* Luca Vizzarro
* Andrew Bailey
####################################################################
Minutes
=====================================================================
General Discussion
* None
=====================================================================
Patch discussions
* RSS Testsuite:
* Patrick to review
* Mbuf fast release testcase / tx_offload:
* Looks good overall
* Most likely the testcase will need to be updated to reflect the latest
tech board decision on mbuf fast free (it is now enabled by default instead
of disabled by default)
* Virtio:
* V2 looks good to Patrick. When it is final - send to Maxime (virtio
maintainer) for his review
* Single_core_fwd_perf:
* Patrick is going to send a V5 which adds a performance_metrics.json
* Traffic Generators are setup and torn down as needed. As a part of
this, Patrick flattened the shell pool system so that there are no longer
testsuite and testcase level shell pools, but this removes some safety (it
stops protecting us from rogue shells which didn’t get closed
* Can we add a flag (like persist) that allows a shell to be added
without being added to the shell pool? Need to ensure this is cleaned up in
testrunteardown
* 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
* Next meeting is Oct 23, 2025
[-- Attachment #2: Type: text/html, Size: 2076 bytes --]
reply other threads:[~2025-11-04 3:35 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='CAJvnSUCgBnw=wXi-1ugP_RYZYMBC2xY2VGBBxv0_WEuekiLYAQ@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).