From: zhoumin <zhoumin@loongson.cn>
To: ci@dpdk.org
Subject: Re: Community CI Meeting Minutes - December 7, 2023
Date: Fri, 8 Dec 2023 06:41:19 +0000 [thread overview]
Message-ID: <e577b8d9-0e61-8721-995b-26d4cbc6e2bb@loongson.cn> (raw)
In-Reply-To: <CAJvnSUCjOabKH_tEpHZqNENRtZrN63cUMMmWB5gfwmTpVNWX2A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3258 bytes --]
Dear team,
On Thur, Dec 7, 2023 at 4:00PM, Patrick Robb wrote:
> December 7, 2023
>
> #####################################################################
> Attendees
> 1. Patrick Robb
> 2. Ali Alnubani
>
> #####################################################################
> Agenda
> 1. General Announcements
> 2. CI Status
> 3. DTS Improvements & Test Development
> 4. Any other business
>
> #####################################################################
> Minutes
>
> =====================================================================
> General Announcements
> * Using the GitHub mirror for CI jobs
> * GHA is totally moved over
> * UNH is partially moved over, and will be completely moved over soon
> * Other labs are also in progress - Patrick is sending reminders
> * There is a webinar right now (9AM EST) about the role of DPDK in 5G
> architecture. If you want to attend once this meeting concludes, link
> is here:
> https://zoom.us/webinar/register/WN_LSyHZj9DRf2Q0XFoev60Sg#/registration
>
> =====================================================================
> CI Status
>
> ---------------------------------------------------------------------
> UNH-IOL Community Lab
> * Have built new container images with baked in ABI references for
> testing 21.11, 22.11, and 23.11
> * 23.11 ABI testing is now online
> * Will upstream the updates to the container image template engine
> to dpdk-ci
> * Octeon board is now completely setup in the chassis - now doing the
> openBMC bringup and Ubuntu installation
> * NVIDIA: The 2nd cx6 NIC is now installed on the DUT, and testing
> approach updated to forwarding packets from interface 0 on NIC A, to
> interface 0 on NIC B. We are seeing better mpps for smaller frame
> sizes, but will continue to iterate on this to reach 100% line rate.
> * Still figuring out what func tests to run
>
> ---------------------------------------------------------------------
> Intel Lab
> * Patrick pinged John McNamara about the STV team using the GitHub
> mirror and who the new maintainer is - will ping again if there is no
> response
>
> ---------------------------------------------------------------------
> Loongarch Lab
> * Zhoumin confirmed to Patrick that he will move the loongson lab ci
> system from git.dpdk.org
> <https://mailgw.loongson.cn/linkserver?dest=http%3A%2F%2Fgit.dpdk.org&tid=_____8CxrusT7HFlRKw_AA--.58868S2&rcpt=zhoumin@loongson.cn&ifnotice=1&rindex=0>
> to the GitHub Mirror
>
LoongArch DPDK ci system had moved from git.dpdk.org to the Github
Mirror on this Wednesday.
Best regards,
Min
> ---------------------------------------------------------------------
> Github Actions
> * Has already moved to GitHub mirror for cloning/fetching
> DTS Improvements & Test Development
> * Juraj and Jeremy agreed that instead of using 2048 rx mbuf size by
> default, but shifting to 1024 mbuf size in (some) cases according to
> the NIC, we should always use 2048 mbuf size. The original design was
> based on the testsuites as written in old dts, but we can see no
> reason for this approach.
>
> =====================================================================
> Any other business
> * Next meeting is December 21, 2023
[-- Attachment #2: Type: text/html, Size: 4639 bytes --]
prev parent reply other threads:[~2023-12-08 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 16:00 Patrick Robb
2023-12-08 6:41 ` zhoumin [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=e577b8d9-0e61-8721-995b-26d4cbc6e2bb@loongson.cn \
--to=zhoumin@loongson.cn \
--cc=ci@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).