From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: dev <dev@dpdk.org>, dts@dpdk.org
Subject: Community CI Meeting Minutes - August 22, 2024
Date: Thu, 22 Aug 2024 16:18:46 -0400 [thread overview]
Message-ID: <CAJvnSUCESyUzuqEdoDEEXK+hQ1oR1Y8nrSteK541XYCgHU53ig@mail.gmail.com> (raw)
#####################################################################
August 22, 2024
Attendees
1. Patrick Robb
2. Tomas Durovec
3. Dean Marx
4. Luca Vizzarro
5. Jeremy Spewock
6. Ali Alnubani
7. Juraj Linkeš
8. Paul Szczepanek
#####################################################################
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
* openssl_asym_autotest driver test is failing on opensuse Leap
* Submitted a bugzilla ticket with
testlogs:https://bugs.dpdk.org/show_bug.cgi?id=1523
* Disabling this in CI testing in the interim
* New Community Lab Servers:
* NVIDIA ConnectX6-Lx and ConnectX7 NICs were moved to the new
servers. The single core performance testing appears good so far (much
better than with the old servers, and having rough parity with the
performance reports NVIDIA publishes on dpdk.org)
* 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 has provided legal approval for AMD to donate 3
additional used servers to the Community Lab, so those will be
arriving soon
* Deployed the update for sending fewer emails to the test-report
mailing list (now we only send an extra email when the overall test
label status updates, or when testing for a patchwork label is 100%
done)
* DTS Check format check:
* Going to run that in CI, should be able to do this by next week
* Also going to start running meson check format with the same process
---------------------------------------------------------------------
Intel Lab
* None
---------------------------------------------------------------------
Github Actions
* None
---------------------------------------------------------------------
Loongarch Lab
* None
=====================================================================
DTS Improvements & Test Development
* MTU update testpmd methods:
* Nick will submit a standalone patch for this, Jeremy and Juraj
will depend on this
* Luca’s pktgen and testpmd change patch includes an implementation
for starting and stopping ports. Everyone should use this method once
the series is reviewed and merged.
http://patches.dpdk.org/project/dpdk/patch/20240806124642.2580828-5-luca.vizzarro@arm.com/
* VF creation:
* Host must have sr-iov setup
* PF is bound to the kernel driver (os_driver in dts)
* Is it important to be non-destructive towards existing VFs when DTS starts?
* People may not expect for DTS to be touching existing system
configuration, and could cause confusion for people who run DTS in
terms of their system state after running DTS
* This is only relevant for bifurcated drivers (mlx5_core)
* Interfaces need to be up (broadcom)
* https://bugs.dpdk.org/show_bug.cgi?id=1500
* Pending Testsuites:
* Some tests require adding functionality to testpmd
* Interrupt_pmd test plan is written from l3fwd-power which has
some hooks for checking wakeups, would need to patch testpmd to fetch
the same info
* https://doc.dpdk.org/dts/test_plans/interrupt_pmd_test_plan.html
* MTU Update is assigned to Alex
* There is probably some discussion on the mailing list about this
suite from years ago, when it was returning inconsistent behavior
across NICs based on assumptions around byte allocations for VLANs
* Might be the exact same issue as arose when the jumboframes
testsuite was written a couple months ago
* Patrick will search for the old mail threads
* Patrick and UNH team need to add more testsuite ideas to the
tracking spreadsheet:
https://docs.google.com/spreadsheets/d/1KrAS0c08x16RddzmYm2RDR93lRYxI9_owfk-9sz6iaI/edit?gid=0#gid=0
* Dts-next branch.
* Paul has been joining the DPDK release meetings, with ARM
updates, and can give dts-next updates too (what is being merged, what
are the important considerations).
* We should summarize the high level for the patches submitted to
the next-dts branch every week, and then Paul can bring that
information to the release meeting if needed.
* Next-dts summary:
* It is not being used yet, but we are going to start now with the
patches which are on patchwork
* So, for example, Luca’s pktgen and testpmd updates series would
be one of the first things which Juraj will add
* Juraj (Next-DTS Maintainer) will be on vacation next week, but
this will be used after
* DTS Docs:
* Dependency issue: pyyaml was a missing dependency, causing docs
build to fail
* .toml file for dependencies uses distro name for pyyaml, so
juraj needed to manually map between these two names
* Resolved in the v19
* Capabilities patch:
* It is done, appears to be working fine in the v3
* Going to extract two patches from this and submit as standalone patches
* Small bugfix for show port info method output
* Caching of port information
* Adds ports info to testpmd instance, grabs that from show port info
* UNH people should provide reviews, run on our hardware
=====================================================================
Any other business
* Next Meeting Sep 5, 2024
reply other threads:[~2024-08-22 20:19 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=CAJvnSUCESyUzuqEdoDEEXK+hQ1oR1Y8nrSteK541XYCgHU53ig@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).