From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: dev <dev@dpdk.org>, Paul Szczepanek <Paul.Szczepanek@arm.com>,
Luca Vizzarro <Luca.Vizzarro@arm.com>,
Dean Marx <dmarx@iol.unh.edu>, Aaron Conole <aconole@redhat.com>
Subject: Community CI Meeting Minutes - August 7, 2025
Date: Tue, 12 Aug 2025 12:33:37 -0400 [thread overview]
Message-ID: <CAJvnSUDrZZsupFkSr+gBXA5aoGJ2BdespKWf143jbK0WsSw43A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 6545 bytes --]
Apologies for the delay in sending these notes out.
#####################################################################
August 7, 2025
Attendees
1. Patrick Robb
2. Luca Vizzarro
3. Dean Marx
4. Aaron Conole
#####################################################################
Minutes
=====================================================================
General Announcements
* Test rechecks:
* DPDK.org patch recheck lab support list has been updated:
https://patchwork.dpdk.org/project/web/patch/20250725163057.1059638-1-probb@iol.unh.edu/
* DTS 25.11 Roadmap:
https://inbox.dpdk.org/dev/CAJvnSUB2scYCkV4BKFyxHVpPLFmhLYVb20tV0LFDeUHLWfVW+Q@mail.gmail.com/
* Luca has been added as a DTS maintainer, taking Paul’s place
=====================================================================
CI Status
---------------------------------------------------------------------
AWS Lab
* None
UNH-IOL Community Lab
* The Community Lab will have downtime for a few hours on Tuesday August
12, for system upgrades
* Pw-ci: Aaron visited the lab last week and was curious about whether the
Community Lab can leverage the pw-ci project, which handles patch polling,
patch apply, etc.
* UNH guys to look at standing this up side by side with our existing
backend to evaluate its usefulness
* https://github.com/ovsrobot/pw-ci
* Had an infra failure on the ARM Grace server this week, and put in
reruns from August 4 - August 6 to correct this.
* Has been stable otherwise.
---------------------------------------------------------------------
Intel Lab
* There were some build failures from Intel CI from the docs build for DTS,
which should be fixed with this patch which removes autodoc_pydantic from
the build:
https://patchwork.dpdk.org/project/dpdk/patch/20250801114547.1128950-1-luca.vizzarro@arm.com/
* Nothing otherwise
---------------------------------------------------------------------
Github Actions Robot
* Started integration of pull request for Sourcery AI analysis.
* This is inadvertently causing testing to run 2x because the extra PR
for Sourcery is being picked up by testing
* Will have to decide which repo for the pull requests to live in, but
it can either be the DPDK repo or ovsrobot repo
* Will publish the pull request link in the checkpatch email, so people
can click it and look at the AI bot’s comments
* If the bot feedback/comments prove useful, then we can look at
setting up a system for sending the bot comments as mails on the mailing
list.
---------------------------------------------------------------------
Loongson Lab
* None
=====================================================================
DTS Improvements & Test Development
* Andrew is adding missing type hints to function args and return types:
https://patchwork.dpdk.org/project/dpdk/patch/20250806162900.273571-1-abailey@iol.unh.edu/
* No new comments
* QinQ: https://patchwork.dpdk.org/project/dpdk/list/?series=35734
* Dean Marxadd a ticket for trackin vlan_tci and vlan_tci_outer as a
later patchseries
* Bruce has produced the following table:
VLAN Stripping Behavior Table
=============================
Input Pkt Tags | VLAN Strip | QinQ Strip | VLAN+QinQ
Strip
---------------------|-------------------|----------------------|----------------------------------
0x8100 | Tag in vlan_tci | -- | Tag in
vlan_tci
---------------------|-------------------|----------------------|----------------------------------
0x88a8 | -- | Tag in vlan_tci_outer| Tag in
vlan_tci_outer
---------------------|-------------------|----------------------|----------------------------------
0x9100 | -- | -- |
--
---------------------|-------------------|----------------------|----------------------------------
| | |
---------------------|-------------------|----------------------|----------------------------------
0x8100 0x8100 | Tag in vlan_tci | -- | Tag in
vlan_tci
---------------------|-------------------|----------------------|----------------------------------
0x8100 0x88a8 | Tag in vlan_tci | -- | Tag in
vlan_tci
---------------------|-------------------|----------------------|----------------------------------
0x8100 0x9100 | Tag in vlan_tci | -- | Tag in
vlan_tci
---------------------|-------------------|----------------------|----------------------------------
0x88a8 0x8100 | -- | Tag in vlan_tci_outer| Tag in
vlan_tci_outer &
| | | tag in
vlan_tci
---------------------|-------------------|----------------------|----------------------------------
0x88a8 0x88a8 | -- | Tag in vlan_tci_outer| Tag in
vlan_tci_outer
---------------------|-------------------|----------------------|----------------------------------
0x88a8 0x9100 | -- | Tag in vlan_tci_outer| Tag in
vlan_tci_outer
---------------------|-------------------|----------------------|----------------------------------
0x9100 [any] | -- | -- |
--
---------------------|-------------------|----------------------|----------------------------------
* VM Virtio Testing:
* For the proof of concept, we are setting a PvP (physical virtual
physical) single VM PoC where both physical functions are leveraged by
virtio devices on the VM.
* Add file management:
https://patchwork.dpdk.org/project/dpdk/list/?series=35807
* Patrick to provide a review today.
* RSS Testsuite: https://patchwork.dpdk.org/project/dpdk/list/?series=35836
* Do we need to run this on any particular hardware?
* Has been tested on E810 and ConnectX6
* UNH guys can try with Broadcom
* Otherwise, Patrick can provide a review.
* Forwarding Performance Test:
* v3 coming in the next few days
* Testcase Docstring Example:
https://patchwork.dpdk.org/project/dpdk/patch/20250722171957.200698-1-dmarx@iol.unh.edu/
* Dean Marx to switch the “steps” to be an unordered list, which will
render better in the docs
=====================================================================
Any other business
* Next Meeting August 21 at the same time
[-- Attachment #2: Type: text/html, Size: 7878 bytes --]
reply other threads:[~2025-08-12 16:40 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=CAJvnSUDrZZsupFkSr+gBXA5aoGJ2BdespKWf143jbK0WsSw43A@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
/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).