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 29, 2024
Date: Tue, 10 Sep 2024 16:00:38 -0400 [thread overview]
Message-ID: <CAJvnSUA+N7125QPRxVOWcw7gSTzYntwkF5VYqp-7CZDomP07Rg@mail.gmail.com> (raw)
#####################################################################
August 29, 2024
Attendees
* Patrick Robb
* Luca Vizzarro
* Paul Szczepanek
* Jeremy Spewock
* Alex Chapman
#####################################################################
Minutes
=====================================================================
General Discussion
* Added a few more unclaimed testsuites to the tracking spreadsheet,
which are a mix of old dts ports and “new” suites:
https://docs.google.com/spreadsheets/d/1KrAS0c08x16RddzmYm2RDR93lRYxI9_owfk-9sz6iaI/edit?gid=0#gid=0
* Alex will take promisc_support & port config persistency
* Some of the UNH students (Dean, Nick) will not be able to attend
these meetings this Fall due to overlapping class schedules. Going
forward we can have them write any notes they want to share in the
minutes the day before the meeting.
* Testsuites which we would like Juraj to look at for next-dts first
when he is in next week?
* “add pktgen and testpmd changes”
* In general we will mostly use this staging branch for framework
updates, but as we have a few testsuites which are ready now, it might
not hurt to apply all of those to next-dts and have thomas/david pull
them from next-dts to main for the first time
* Mac_filter
* Blocklist?
* L2fwd?
* Jeremy to break out IP update (if not set by user) commit from
dynamic_queue as this could also be applied to next-dts
* Xml-rpc server replacement
=====================================================================
Patch discussions
* Capabilities patch:
* Jeremy has left a review, Nick is in progress with his
* UNH folks are reviewing luca’s testsuite patches this week (lwf2d, blocklist)
* Verbose output:
* One option to preserve the current verbose output would be to
maintain the format and set of contents as the base behavior for
verbose output, but add a flag which will print the current output +
other info such as l4 port #
=====================================================================
Bugzilla discussions
* None
=====================================================================
Any other business
* Next meeting Sep 12, 2024
reply other threads:[~2024-09-10 20:01 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=CAJvnSUA+N7125QPRxVOWcw7gSTzYntwkF5VYqp-7CZDomP07Rg@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).