From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: DTS WG Meeting Minutes - July 3, 2025
Date: Tue, 8 Jul 2025 18:57:49 -0400 [thread overview]
Message-ID: <CAJvnSUBiROu1_iOCb_hPKGF+ggOkRLgeQ0=95oVCmE3ir5DCpw@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUCDkunBMDbh+VH2Nzzf-R-h6-PNG-xAJY_zQfRNmhTF7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]
On Tue, Jul 8, 2025 at 6:56 PM Patrick Robb <probb@iol.unh.edu> wrote:
> #####################################################################
> July 3, 2025
> Attendees
> * Patrick Robb
> * Manit Mahajan
> * Dean Marx
>
> #####################################################################
> Minutes
>
> =====================================================================
> General Discussion
> * NA
>
> =====================================================================
> Patch discussions
> * Merged since last meeting:
> * doc: elaborate on per test suite configuration dts docs
> * Devbind initialization bug
> https://patchwork.dpdk.org/project/dpdk/patch/20250616183859.646384-1-dmarx@iol.unh.edu/
> * Fix deterministic doc
> https://patchwork.dpdk.org/project/dpdk/patch/20250611140530.51551-1-cfamullaconrad@suse.com/
> * L4 port # packet matching
> * Packet capture testsuite:
> https://patchwork.dpdk.org/project/dpdk/patch/20250506132933.1580584-4-luca.vizzarro@arm.com/
> * Current development:
> * Single_core_forwarding perf test:
> * Patrick submitting a new version today
>
Although the single core forwarding test is running, there are some updates
required for the patch which were too significant to fit into this release,
so it has been pushed to the next DPDK release.
> * VF support and testsuite
> * Dean submitted new version - this one has VF creation logic moved
> to topology.py and properly resets sut ingress port and sut egress port to
> the VFs
> * Only supports 1 VF per PF. This allows us to validate most of
> the VF capabilities we are interested in testing, but may limit us on
> testing certain workloads
> *
> https://patchwork.dpdk.org/project/dpdk/patch/20250617201358.708638-1-dmarx@iol.unh.edu/
>
> =====================================================================
> Bugzilla discussions
> * None
>
> =====================================================================
> Any other business
> * Next meeting is Jul 17, 2025
>
[-- Attachment #2: Type: text/html, Size: 3112 bytes --]
prev parent reply other threads:[~2025-07-08 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 22:56 Patrick Robb
2025-07-08 22:57 ` Patrick Robb [this message]
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='CAJvnSUBiROu1_iOCb_hPKGF+ggOkRLgeQ0=95oVCmE3ir5DCpw@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).