DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org, dts@dpdk.org
Subject: DTS WG Meeting Minutes - August 15, 2024
Date: Thu, 15 Aug 2024 12:54:19 -0400	[thread overview]
Message-ID: <CAJvnSUCmacKJBExFVKPtyz9Bny6kAXQKgCvxF20WckzruSW01g@mail.gmail.com> (raw)

#####################################################################
August 15, 2024
Attendees
* Patrick Robb
* Jeremy Spewock
* Alex Chapman
* Juraj Linkeš
* Tomas Durovec
* Dean Marx
* Luca Vizzarro
* Paul Szczepanek
* Nicholas Pratte

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

=====================================================================
General Discussion
* DTS Roadmap: https://docs.google.com/document/d/1Rcp1-gZWzGGCCSkbEsigrd0-NoQmknv6ZS7V2CPdgFo/edit
   * Will email out after this meeting
* Speakers are all signed up for the CI and DTS talks at DPDK Summit

=====================================================================
Patch discussions
* Testpmd shell method names: should they align with existing testpmd
runtime commands? I.e. should the “flow create” runtime command be
implemented via a method named flow_create_*() or the more english
intuitive create_flow_*()
   * One option is to implement both, and have one method call the other
      * This potentially creates confusion as people read different
testsuites and see different functions used, not realizing they may be
the same
   * The group agrees it is best to name methods in a human readable
intuitive way… so like create_flow_*() from the example above.
* Testpmd verbose parser
   * If we read port from testpmd to identify packets, they must have
a tcp/udp layer, which may be limiting. If, for whatever reason,
packets for a testsuite cannot be built with a l4, individual
testsuites may have to check based on src mac address, checksum etc.
   * In almost all cases, packets can be build with a l4
* Checksum offload suite is submitted
   * Dependency on the existing testpmd verbose parser
   * RX side testcases work fine, but TX side behavior is not aligning
with what is described in the testsuite, so feedback on this is
appreciated
   * Checksum offload command
      * Csum set {layer name} hw {port number}
      * Returns sctp offload is not supported
      * TCP/UDP packets are working
* Port assignment:
   * Physical ports are defined in the nodes conf section, then port
ids are referred to in the testrun config
   * Also includes splitting the nodes and testrun configs into different files
      * Discussion on ticket regarding having a conf directory to contain these
   * Still some work to be done removing unneeded configuration from conf.yaml
* VXLAN-GPE testsuite is now canceled as the feature is removed as of DPDK 24.07
* API Docs
   * Juraj needs reviews and testing
   * UNH people please rebuild the docs and provide your experience
      * Should specifically test meson install
   * Aim is to make it simple to use (and it is)
   * It builds with DPDK docs
* L2fwd
   * Jeremy provided a review, more people at UNH please run this and
provide feedback
   * When reviewing people should also review the dependency - add
pktgen and testpmd change series
* Tomas and Juraj have begun work on producing the testrun results json

=====================================================================
Bugzilla discussions
* None

=====================================================================
Any other business
* Next meeting Aug 29, 2024

                 reply	other threads:[~2024-08-15 16:54 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=CAJvnSUCmacKJBExFVKPtyz9Bny6kAXQKgCvxF20WckzruSW01g@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).