From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org
Subject: DTS WG Meeting Minutes - April 24, 2025
Date: Fri, 25 Apr 2025 10:19:21 -0400 [thread overview]
Message-ID: <CAJvnSUDdkMSqTGJfA6ZVWymBKDx883rAd2hAMT-=AdsiqdFazQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2816 bytes --]
#####################################################################
April 24, 2025
Attendees
* Patrick Robb
* Luca Vizzarro
* Paul Szczepanek
#####################################################################
Minutes
=====================================================================
General Discussion
* DPDK Prague will be held on May 8-9
* Due to overlap, we will not hold a DTS meeting call on May 8, which
would have been the next regularly scheduled meeting
* Patrick needs to cancel this on LF events
=====================================================================
Patch discussions
* RTE_FLOW email thread has some updates, including Thomas’s suggestions
for test coverage and Dean’s new rough test plan:
*
https://inbox.dpdk.org/dev/CABD7UXPfQcvLt4a5YrxSUaH5NNRJzZHjHUtXs9G-jBnNkiJw8w@mail.gmail.com/
* Review discussion:
* HIGH PRIORITY:
* Shell refactoring patchseries:
https://patchwork.dpdk.org/project/dpdk/list/?series=34865
* We really need this done - Patrick has blocked out his 3pm-5pm
today to get this reviewed and tested
* Medium priority:
* L4 port # packet matching:
https://patchwork.dpdk.org/project/dpdk/list/?series=34805
* Patrick to review/merge to next-dts
* RSS testsuites:
https://patchwork.dpdk.org/project/dpdk/list/?series=34713
* Has a partial review - Thomas will submit a new version
* Dean is also looking through this testsuite as it pertains to
flow rules
* Tmp dir and dpdk tree dir:
https://patchwork.dpdk.org/project/dpdk/list/?series=35049
* * Low Priority:
* Nick submitted his RFC for adding performance TG support:
https://patchwork.dpdk.org/project/dpdk/list/?series=35097
* TG abstraction structure is up for discussion and can be changed
* We will start writing the single core forwarding perf test while
we wait for reviews
* Merged patchseries:
* Port_stats testsuite has been merged
* Old testsuites:
* Patrick rebased/updated and resubmitted the port_control testsuite.
But I found one more change which is needed just now - can submit that
today.
* The other old patches from Jeremy have been re-tagged to “changes
requested” on patchwork, and Patrick will be working through these.
=====================================================================
Bugzilla discussions
* None
=====================================================================
Any other business
* There will be a “Birds of a feather” session at DPDK Prague, which we
could suggest a topic for:
* Idea #1: DTS Testsuite API/module. What functions are currently
exposed to testsuites, and what others can be added in the future?
* Next meeting is May 22, 2025
[-- Attachment #2: Type: text/html, Size: 3474 bytes --]
reply other threads:[~2025-04-25 14:23 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='CAJvnSUDdkMSqTGJfA6ZVWymBKDx883rAd2hAMT-=AdsiqdFazQ@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).