From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org, dts@dpdk.org
Subject: DTS WG Meeting Minutes - November 7, 2024
Date: Thu, 7 Nov 2024 10:45:51 -0500 [thread overview]
Message-ID: <CAJvnSUAukDDNtF=Uk0-oKUt38eqT9ngqPnmwwGcAgayL-cwGpw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3585 bytes --]
#####################################################################
November 7, 2024
Attendees
* Patrick Robb
* Paul Szczepanek
* Thomas Wilks
* Luca Vizzarro
#####################################################################
Minutes
=====================================================================
General Discussion
* 24.11 roadmap status:
https://docs.google.com/document/d/1doTZOOpkv4D5P2w6K7fEJpa_CjzrlMl3mCeDBWtxnko/edit
* We should prioritize reviews and merging over further developing at this
time.
* DPDK Release schedule:
* RC2 is not yet merged. Most likely this will happen November 8.
* RC3 should be 11/15
* Release should be 11/27
=====================================================================
Patch discussions
* DTS Docs bugfix: moves DTS docs to the same dir as dpdk docs
* Paul has provided this patch this morning:
https://patchwork.dpdk.org/project/dpdk/patch/20241025103520.394951-1-paul.szczepanek@arm.com/
* We have been told to merge this to next-dts (previously we thought it
was going direct to main), so Paul is applying this to next-dts after this
meeting.
* Copying DPDK build to SUT
* Merged last week, and was tested with tarball and dpdk tree options on
both test engine node and SUT node
* Pydantic patchseries:
* https://patchwork.dpdk.org/project/dpdk/list/?series=32823
* V5 was submitted with some improvements, including how dataclass
fields display in the API docs (prevents field duplication)
* Dts docs building instructions are to build the docs from the
poetry environment (with those dependencies installed)
* Patrick did not build api docs from this patch but can do so if
needed
* Removes warlock dependency from poetry
* Patrick will both build the api docs outside of poetry, and do a
sanity check testrun, then he will apply to next-dts today.
* Some issues observed with types in scapy 2.6 and above
* We should most likely pin this (and everything) instead of just
setting a minimal version supported via poetry
* Patrick will continue merging testsuites, including mac_filter,
dual_vlan, dynamic_config (needs to be rebased for new testpmd_shell
functions introduced in the capabilities series), blocklist and l2fwd if
submitted, etc.
* L2fwd and blocklist should be updated by UNH guys and merged
* Nick’s patch for removing excess config attributes:
* Nick can text Luca for pydantic knowledge as needed to speed this up.
* Updating mypy results in some linter warnings reported
* This can be addressed in 25.03
* Per testsuite configs: Luca has something to submit for this
* Asyncsniffer bug seen with intel nics
* Nick submitted a patch which just adds a sleep 1000ms before sniffing
* Paul is advocating for a deterministic approach in which the sequence
of events for triggering the sniffer and sending packets is changed.
* Is there a programmatic way of verifying the readiness of the
asyncsniffer?
* There may be a listen with some return code we can use (check the
scapy api). May be possible to keep probing this until we get the right
answer.
=====================================================================
Bugzilla discussions
* We should add a bugzilla ticket for discussing fuzz testing in DTS
* Patrick can add
* API docs do not include the testsuites, so this needs to be added
* Patrick make a ticket for this
=====================================================================
Any other business
* Next meeting Nov 21, 2024
[-- Attachment #2: Type: text/html, Size: 4054 bytes --]
reply other threads:[~2024-11-07 15: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='CAJvnSUAukDDNtF=Uk0-oKUt38eqT9ngqPnmwwGcAgayL-cwGpw@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).