DPDK CI discussions
 help / color / mirror / Atom feed
* DTS WG Meeting Minutes - September 12, 2024
@ 2024-09-12 20:41 Patrick Robb
  0 siblings, 0 replies; only message in thread
From: Patrick Robb @ 2024-09-12 20:41 UTC (permalink / raw)
  To: dev; +Cc: ci, dts

#####################################################################
September 12, 2024
Attendees
* Patrick Robb
* Paul Szczepanek
* Alex Chapman
* Luca Vizzarro
* Jeremey Spewock
* Juraj Linkeš

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

=====================================================================
General Discussion
* UNH Lab CI items:
   * Jeremy has written the Jenkins automation for Running and
reporting results from new DTS. We are dry running this and watching
it for a couple days but are targeting enabling this for Monday
      * Will just run the scatter suite now, but we will enable more
suites as they reach main
   * UNH guys are still writing the automation for running the dts
check format script, but are almost done and aim to have this online
early next week.
* DTS testsuites tracking spreadsheet:
https://docs.google.com/spreadsheets/d/1KrAS0c08x16RddzmYm2RDR93lRYxI9_owfk-9sz6iaI/edit?gid=0#gid=0
* Q4 arm plans
   * Alex’s internship will be ending in 2 weeks time
   * There will be a new apprentice at arm (Thomas) who will writes
testsuites - Luca will be working on framework updates
      * Possible framework improvements:
         * testpmd module clean up
         * Parallel functional tests on the SUT
            * https://bugs.dpdk.org/show_bug.cgi?id=1353
         * Scapy packet generation (can these be leveraged by trex)
         * Spinning up VMs and running testing - need to gather more
info, but initial ticket created:
https://bugs.dpdk.org/show_bug.cgi?id=1541
         * Adding interactive shells for other critical DPDK apps
         * Adding perf traffic generator implementations (trex, dperf,
dpdk-pktgen)

=====================================================================
Patch discussions
* Some patches are merged to next-dts, most significantly Luca’s patch
which adds support for sending random packets, sending a list of
packets, and adds some testpmd_shell methods for common runtime
commands
* Many testsuites no longer apply cleanly (expected). In order to
decrease the work associated with this, it makes sense to tighten the
loop between requesting a rebase and resubmission, and application to
next-dts.
   * Maintainer can locally resolve any issues in some cases
* Some series look good but need to be rebased from next-dts:
   * Adjust l2/l3 addresses when not set:
https://patchwork.dpdk.org/project/dpdk/patch/20240904152827.11914-2-jspewock@iol.unh.edu/
   * Xml-rpc server replacement:
https://patchwork.dpdk.org/project/dpdk/patch/20240625211114.886-2-jspewock@iol.unh.edu/
* Driver binding on tg:
https://patchwork.dpdk.org/project/dpdk/patch/20240812172251.41131-2-jspewock@iol.unh.edu/
   * Confirmed this does not result in an additional dpdk build on the
TG node, so this should be good to go
* VF testing
   * Oftentimes there will be two test suites that are testing the
same test cases, but one is for PFs and one is for VFs in Old DTS but
this is something that we obviously want to avoid.
   * Luca brought up the idea of just writing one test suite, and
specifying in the test run whether you want it to be run on VFs or
PFs.
      * This would make things a lot easier since it would be more
abstract for the developer
      * It would however make it so that you cannot run both pf and vf
testing in the same run unless we did it on a per-test suite basis.
   * Right now Jeremy wrote vf_smoke and just made it inherit from the
pf_smoke class and abstracted which ports it uses and this works as
well.
   * Running idea: We will pursue the route of only having one test
suite and having some kind of configuration value that decides whether
it is VF or PF
      * Should still keep results distinct from VF runs of a suite vs PF ones
      * Luca’s per-testsuite config might be a good candidate for this
since it allows you to specify test suite configuration values in
conf.yaml

=====================================================================
Bugzilla discussions
* Added a new ticket for updating pw_maintainers_cli.py script (which
guesses which tree to apply a DPDK patch on) to add support for
next-dts: https://bugs.dpdk.org/show_bug.cgi?id=1540

=====================================================================
Any other business
* Next meeting Sep 26, 2024
* New Maintainer
   * Since Juraj will have to relinquish his maintainership of dts,
Luca Vizzarro (ARM) and Patrick Robb (UNH-IOL Community Lab) should
volunteer to be co-maintainers

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2024-09-12 20:42 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-09-12 20:41 DTS WG Meeting Minutes - September 12, 2024 Patrick Robb

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).