From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org
Subject: DTS WG Meeting Minutes - November 6, 2025
Date: Fri, 12 Dec 2025 14:49:56 -0500 [thread overview]
Message-ID: <CAJvnSUBnV5aPjrcysV0BS9c4H-j8rfvfAA=da7c9ZW0H5FmvCg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2641 bytes --]
November 6, 2025
Attendees
* Patrick Robb
* Luca Vizzarro
* Andrew Bailey
* Paul Szczepanek
Minutes
General Discussion
* RC2 will release at the end of the week
* DPDK build fails if pydantic is installed, because there are pydantic
warnings with DTS:
* idea A is to have pydantic installed and do a doc build before sending
a patch, then fix any warnings if they exist
* If we want to test the DTS build in CI, we would have to install
the DTS dependencies and run a dpdk build
* BaseConfig testsuite configuration is causing a build failure this
week, as it is not loaded except for at runtime (so, not the doc build)
* No, we don’t have any new ideas.
* We got feedback that docs need clarification regarding the API vs
Framework usage.
* Realistically, given the RC timeline, we will need to update docs
noting that the API is in a transitionary period
* Otherwise, keep plugging away at removing framework imports and then
this problem will be solved.
Patch discussions
* Mbuf fast release testcase / tx_offload:
* Merged
* add test case docstring checks to format script
* Dean is updating this series
* doc: add test case docstring example to dts rst
* Patrick to merge the first patch. The second patch is superseded and
won’t be merged.
* Virtio:
* We are transmitting 100 packets to the SUT (should go from physical
nic to virtio frontend to vhost backend, then back through to the TG again
for sniffing) but we are seeing ~350 packets forwarded in the vhost backend
which seems wrong.
* Paul has suggested that we check that the extra packets aren’t
coming from another source other than the TG scapy.
* [v2] dts: testpmd link check on port start
* Andrew reviewing. Can be applied ASAP.
* Single_core_fwd_perf:
* New version sent. Need to resolve a build issue with the Intel CI Lab.
* V6 just addresses some nits from Luca and Andrew
* API:
* Artifact series is merged
* Further changes:
* RSS:
* Patrick has tested
* Imports have to be updated for /api/, but this can be done by Patrick
at merge time if no further change are required.
* Patrick to merge
* QinQ:
* Dean has tested and it is working
* Patrick will also do a test, and a final review
* TCI:
* During the 26.03 release, Dean to add a secondary part to this
testsuite that not only checks that packets are modified correctly by vlan
and qinq stripping, but that the TCI and OUTER_TCI fields are being written
to correctly.
Bugzilla discussions
* None
Any other business
* Next meeting is Nov 20, 2025
[-- Attachment #2: Type: text/html, Size: 2814 bytes --]
reply other threads:[~2025-12-12 19:51 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='CAJvnSUBnV5aPjrcysV0BS9c4H-j8rfvfAA=da7c9ZW0H5FmvCg@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).