DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org, Dean Marx <dmarx@iol.unh.edu>,
	Luca Vizzarro <Luca.Vizzarro@arm.com>,
	 Paul Szczepanek <Paul.Szczepanek@arm.com>,
	Aaron Conole <aconole@redhat.com>,
	 Maxime Coquelin <maxime.coquelin@redhat.com>,
	Andrew Bailey <abailey@iol.unh.edu>,
	 Manit Mahajan <mmahajan@iol.unh.edu>,
	"Brandes, Shai" <shaibran@amazon.com>,
	 "Gao, DaxueX" <daxuex.gao@intel.com>
Subject: Community CI Meeting Minutes - August 21, 2025
Date: Mon, 25 Aug 2025 13:49:43 -0400	[thread overview]
Message-ID: <CAJvnSUDRLR74-HRpg+MPzHUR5h+7HNN2ax_rHuZ4c4+Hv-Bm6Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 5670 bytes --]

#####################################################################
August 21, 2025
Attendees
1. Patrick Robb
2. Luca Vizzarro
3. Maxime Coquelin
4. Dean Marx

#####################################################################
Minutes

=====================================================================
General Announcements
* None

=====================================================================
CI Status

---------------------------------------------------------------------
AWS Lab
* How can we access a EC2 ENA instance(s) to test DTS with?
   * Patrick emailed Shai asking if he can get a credit for us to book
something - no word yet
   * Otherwise, Patrick might be able to just get a little spend auth from
the UNH Lab to do this
* Otherwise, AWS Lab has been running consistently.

---------------------------------------------------------------------
UNH-IOL Community Lab
* DTS: From reviewing DTS results from previous weeks, there are 3
testsuites that are occasionally (like 1% of testruns) reporting a false
failure due to dropping packets:
   * Scatter
   * Vlan
   * Packet_capture
   * Checksum offload
   * UNH team to remove these from CI temporarily and check their packet
matching scheme for an implementation issue
   * Patrick to create tickets for these testsuite
* Pw-ci: UNH guys have not deployed an instance of this yet but it’s in the
queue.

---------------------------------------------------------------------
Intel Lab
* None
* They had a failure for the mbuf_fast_free tx_offload testcase in legacy
DTS. Morten and the intel lab team had a back and forth. Morten has now
rewritten the testplan for mbuf_fast_free.

---------------------------------------------------------------------
Github Actions Robot
* None

---------------------------------------------------------------------
Loongson Lab
* None

=====================================================================
DTS Improvements & Test Development
* Virtio VM testing:
   * One path is a vhost + Virtio type scenario where we are sending
packets between physical systems
   * It may be a good idea to have a test not involving physical NICs,
would make it easier to test for contributors broadly.
   * Vhost kernel is an accel implementation for TAP interfaces
   * Another option to simplify is to have vhost kernel for providing TAP
interface, and connecting to virtio_user PMD, don’t create a VM. Will not
be testing the pci layer, rather the virtio-user PMD directly connected to
the TAP interface, but the datapath will be the same.
      * Does not require having a VM to be installed, which reduces the
setup burden both for DTS framework and for the “user” in terms of system
dependencies
   * Doc:
https://doc.dpdk.org/guides/howto/virtio_user_as_exception_path.html
      * Our first virtio testsuite will use this method
   * Doc:
https://doc.dpdk.org/guides/howto/virtio_user_for_container_networking.html
   * Could test vduse - create vhost-vdpa devices
      * Can connect to QEMU like you can connect vhost-user devices
      * Or can connect to virtio_user PMD
      * But, this is lower priority
   * If DTS team has questions, we can reach out to Maxime on Slack.
   * Vhost virtio test without a VM would be using virtio vdevs for testpmd
on the host
* Enable driver binding on the TG:
   * Patrick thinks the implementation looks good. He ran a testrun from
this patch with the TG driver unbound, and it did correctly bind, but then
the link was down on the TG interface so the sniffer could not be created.
   * Patrick to check where the ip link set dev up command is run in the
port setup, and see if that is missing now, or if it is being called too
early, or something else.
* Andrew is adding the mbuf_fast_free testcase to new DTS based on Morten’s
testplan.
* artifacts: https://patchwork.dpdk.org/project/dpdk/list/?series=35807
   * Will submit a new version in the next few weeks
   * Original intention was to have a global log and a testsuite specific
log.
      * There is no intention to have testcase specific log files (as is
the case with the V1)
* QinQ strip: Next step is to test on Broadcom and share back to Ajit and
maybe Morten/Bruce if those results are meaningful
* RSS: Patrick needs to do a review on this ASAP
   * This is top priority for the UNH guys
* Change default topology to 1 link:
   * Patrick to merge
   * https://patchwork.dpdk.org/project/dpdk/list/?series=35971
* Docs updates:
   * Fix missing type hints (Andrew is working on this)
   * Rewrite steps and verify sections, and add a new script under
dts-check-format which validates conformance to this test/verify docstring
for each testcase (Dean has submitted this)
      * The python check script that Dean is proposing to add to the DPDK
devtools dir needs to be prefixed with dts-* in the name so that it is
clear it is to be used for DTS
   * Reduce duplication between module docstrings, class docstrings, and
function docstrings. Thomas Wilks will work on this one.
* Remove test_ prefix from testcases:
https://patchwork.dpdk.org/project/dpdk/patch/20250820151215.47742-1-dmarx@iol.unh.edu/
   * Patrick to merge this
* Adding missing type hints:
https://patchwork.dpdk.org/project/dpdk/patch/20250820151850.484576-1-abailey@iol.unh.edu/
   * Patrick to give a final review and merge it
* API dir:
   * Goal is that tests only import from api/* and nothing from framework/*

=====================================================================
Any other business
* Next Meeting is Sep 4, 2025

[-- Attachment #2: Type: text/html, Size: 6457 bytes --]

                 reply	other threads:[~2025-08-25 17:56 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=CAJvnSUDRLR74-HRpg+MPzHUR5h+7HNN2ax_rHuZ4c4+Hv-Bm6Q@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=Luca.Vizzarro@arm.com \
    --cc=Paul.Szczepanek@arm.com \
    --cc=abailey@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=daxuex.gao@intel.com \
    --cc=dev@dpdk.org \
    --cc=dmarx@iol.unh.edu \
    --cc=maxime.coquelin@redhat.com \
    --cc=mmahajan@iol.unh.edu \
    --cc=shaibran@amazon.com \
    /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).