From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: dev <dev@dpdk.org>, dts@dpdk.org
Subject: Community CI Meeting Minutes - September 5, 2024
Date: Tue, 10 Sep 2024 16:06:13 -0400 [thread overview]
Message-ID: <CAJvnSUDcDH49snmAWZmm8SgDFeN1Wyq7WpvAWOqaPTLgqihCPA@mail.gmail.com> (raw)
#####################################################################
September 5, 2024
Attendees
1. Patrick Robb
2. Ali Alnubani
3. Jeremy Spewock
4. Juraj Linkeš
5. Luca Vizzarro
6. Alex Chapman
7. Paul Szczepanek
8. Aaron Conole
#####################################################################
Minutes
=====================================================================
General Announcements
* DPDK Summit Montreal: September 24-25
* Some Summit attendees will be visiting the UNH Community Lab on
September 26.
=====================================================================
CI Status
---------------------------------------------------------------------
UNH-IOL Community Lab
* New Community Lab Servers:
* NVIDIA: Patrick is experimenting with some more of the AMD
specific optimization system configs:
* https://doc.dpdk.org/guides/linux_gsg/amd_platform.html
* https://www.amd.com/system/files/documents/58017-amd-epyc-9004-tg-data-plane-dpdk.pdf
* Linux Foundation Legal is drafting the agreement with AMD for
them to donate 3 used servers to the community lab, so that’s still in
progress.
* Supermicro has all the documents they need from UNH to continue
with a purchase for an ARM Grace server at the Community Lab. Patrick
has asked for 1 more build modification, which SMC sales has forwarded
on.
* UNH team is still writing the automation scripts for reporting the
check-meson and dts-check-format devtools checks.
* The embedded grafana visualization at
https://lab.dpdk.org/results/dashboard/stats/ the Community Lab
Dashboard stats page is broken. The team will resolve and re-deploy
asap.
---------------------------------------------------------------------
Intel Lab
* None
---------------------------------------------------------------------
Github Actions
* None
---------------------------------------------------------------------
Loongarch Lab
* None
=====================================================================
DTS Improvements & Test Development
* Pantheon’s contract with ARM is concluding at the end of September,
meaning that Juraj will no longer be working on DTS after September.
* A new maintainer volunteer is needed
* Maybe Patrick
* Maybe someone from ARM
* Other volunteers are welcome
* Patches which they will be trying to wrap up this month:
* API Docs Generation
* Capabilities checks
* Externally compiled DPDK
* Results JSON
* Next-dts patches to be merged on Monday:
* add pktgen and testpmd changes
* Mtu modification:
https://patchwork.dpdk.org/project/dpdk/patch/20240826211327.16082-2-jspewock@iol.unh.edu/
* API Docs generation patch
* UNH folks will do some more runs with the testsuite patches and
add tags (to be done before Monday)
* No movement on the discussion regarding adding l4 port to testpmd
verbose output
* https://core.dpdk.org/roadmap/ RFC deadline is September 7
=====================================================================
Any other business
* Next Meeting Sep 19, 2024
reply other threads:[~2024-09-10 20:07 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=CAJvnSUDcDH49snmAWZmm8SgDFeN1Wyq7WpvAWOqaPTLgqihCPA@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dts@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).