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 1, 2024
Date: Thu, 1 Aug 2024 15:39:10 -0400 [thread overview]
Message-ID: <CAJvnSUD_RtmomknkqKcPjpj=w62F1mgbw-fzc-+vgFUBCQy=DA@mail.gmail.com> (raw)
August 1, 2024
#####################################################################
Attendees
* Patrick Robb
* Jeremy Spewock
* Nicholas Pratte
* Juraj Linkeš
* Alex Chapman
* Luca Vizzarro
#####################################################################
Minutes
=====================================================================
General Announcements
* DPDK 24.07 is released
* DPDK Summit CFP deadline has passed. Luca submitted a talk for
setting up DTS and running testsuites. Patrick submitted a talk for CI
Labs/community update and new CI testing coverage, tools, etc.
available to DPDK developers.
* Draft of DTS 24.11 roadmap:
https://docs.google.com/document/d/1Rcp1-gZWzGGCCSkbEsigrd0-NoQmknv6ZS7V2CPdgFo/edit
* Do we want to add DTS items to release notes?
* What is the process for building the release notes? Should the
people working on DTS aggregate the updates and submit them? Patrick
Robbshould check the website for the release notes process, or email
the dev mailing list asking.
* Dpdk-next-dts has been set up: https://git.dpdk.org/next/dpdk-next-dts/
* We should continue to submit patches like normal. Juraj will
apply the patches to next-dts as needed.
* Once the patches are in next DTS for-main branch, they can be
pulled into DPDK main at any time by Thomas/David
* Some AWS engineers are invited to the CI call for next week.
* Will talk about reporting publicly using their internal tooling
* Will talk about reporting using dpdk-test from AWS
* Will (possibly) talk about DTS at AWS
=====================================================================
Patch discussions
* Adding support for DTS creating device VFs:
* Shouldn’t need any additions to the config file.
* There can be a capability associated with this, i.e. this
testsuite requires VFs, then we run “dpdk-devbind.py -s” and parse out
the output for available VFs.
* Method for creating the VFs can return the list of VFs which can
be stored in the testsuite object as VF ports
* Ipv4_reassembly: not eth_dev, will not be implemented in new DTS.
* Patrick Robbneeds to strike through this row, and give Luca edit
access on the spreadsheet
* We need to add more testsuites to the list. Dean Marxand Patrick
Robbshould sync on this to discuss the new list that Dean put
together, and find some more cases.
* We often ship testsuites patches and testpmd shell additions
together, and the testpmd shell addition gets locked up for an
extended period of time as the testsuite gets reviews. If we spit out
the testsuite additions and the framework additions, we can merge the
framework additions quickly into the dts staging branch. For now, we
can ship testsuite patches and their respective framework updates
together, and split them out if we reach the 2nd half of a release
cycle and we need to start moving.
=====================================================================
Bugzilla discussions
* Looking into submitting a bugzilla ticket for mlx5 NICs not
distinguishing between having a bad checksum and having no checksum in
testpmd verbose output.
=====================================================================
Any other business
* Next meeting Aug 15, 2024
reply other threads:[~2024-08-01 19:39 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='CAJvnSUD_RtmomknkqKcPjpj=w62F1mgbw-fzc-+vgFUBCQy=DA@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).