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
Subject: DTS WG Meeting Minutes - March 27, 2025
Date: Mon, 31 Mar 2025 20:42:58 -0400	[thread overview]
Message-ID: <CAJvnSUCXK4A_SLqoQvhRJo95EcbYt2MfZ4zOHF3xLjO0F+miBg@mail.gmail.com> (raw)

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

#####################################################################
March 27, 2025
Attendees
* Patrick Robb
* Luca Vizzarro

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

=====================================================================
General Discussion
* DPDK 25.03 has been released
* We are aggregating the patches/tickets for the 25.07 DTS roadmap. Initial
proposals are:
   * 1. TG abstraction rework (to facilitate performance TGs), testsuite
API additions for perf workloads, and TREX class implementation
      * Luca raised that it may be best to leave the perf TGs as child
classes of the current tg abstract class and simply not implement the
capturing methods
      * Luca also raises that his asyncsniffer patchseries adds some new
methods of collecting packets, such as collecting until a stop condition is
met (like seeing packet X). This may split out packet send and packet
capture from send_packet_and_capture(), making them independent.
   * 2. Write testsuite perf_single_core_fwd
   * 3. Write testsuite rte_flow
   * 4. Port VF support
   * 5. Docs improvements for new users
      * Luca has indicated that Thomas Wilks will contribute to this
   * 6. Smoke test tweaks to ensure they are not a setup burden
   * 7. Rework packet send and receive functions in the Testsuite API
towards supporting IP networking in an L3 environment
   * 8. DPDK Testsuite API: This will provide a stable API which will not
be broken going forward (except at agreed upon intervals)
   * 9. RSS Support Testsuites
      * Work for this is basically done - reviews needed though:
https://patchwork.dpdk.org/project/dpdk/list/?series=34713
   * 10. Non-Development roadmap goals include: Filming a video series
explaining DTS usage, scheduling syncs with testers/developers from DPDK
member companies to introduce them to DTS.
   * 11. Update TestResult module in order to give a more human readable
summary of the testsuites
   * 12. Improved interactive shell data collection and logging.
      * Add a file which exclusively logs the shell interactions
   * 13. Add dedicated file manager to handle passing files and artifacts
between the test engine and nodes in a path agnostic manner
      * This will be a component of the new DPDK DTS API
   * 14. Flexible port binding
      * Give the opportunity to test suites to use all or part of the
supplied port topology with the kernel drivers (instead of DPDK). Could be
achieved with a decorator
      * This will require the Topology class to be aware of what’s truly
available for DPDK and provide only the right ports for it
   * Move these over to:
https://docs.google.com/document/d/1doTZOOpkv4D5P2w6K7fEJpa_CjzrlMl3mCeDBWtxnko/edit?tab=t.0
* This is a friendly reminder that when you start working on a testsuite,
you should make sure there is a ticket documenting that on DPDK/DTS bugzilla
* Smoke tests do not run from next-dts currently, due to a patch from the
per-test-suites-configuration patch from the end of 25.03.
   * Patrick will submit a fix
   * Also, it is worth discussing the usefulness of the smoke tests
generally:
      * Some tests are confirming simple setup correctness and help
validate DTS has been configured right, while others are testing DPDK more
broadly (like the dpdk-test runs) and may pose a burden to developers
         * One option is to keep the smoke tests as they are but default
them to off instead of on

=====================================================================
Patch discussions
* Per testsuite configuration:
   * merged
* VF port support:
   * In progress
* TREX perf TG support:
   * RFC should be submitted this week or next
Bugzilla discussions
* Thomas M cleaned up the Bugzilla board some
* Patrick cleaned up some other tickets - worth taking 1 more look at it
will Paul at a future meeting.
* No other Bugzilla discussion

=====================================================================
Any other business
* Next meeting is April 10, 2025

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

                 reply	other threads:[~2025-04-01  0:47 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=CAJvnSUCXK4A_SLqoQvhRJo95EcbYt2MfZ4zOHF3xLjO0F+miBg@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dev@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).