From: Owen Hilyard <ohilyard@iol.unh.edu>
To: dev <dev@dpdk.org>, dts@dpdk.org
Subject: DTS WG Meeting Minutes 1/19/22
Date: Wed, 26 Jan 2022 10:06:28 -0500 [thread overview]
Message-ID: <CAHx6DYB8=+o+dg42TN_3R4oR3CuP6kCDruyGZ9d31ZS+-2e9HA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3676 bytes --]
Hello Everyone,
Sorry about being so late in sending these out.
This document will always be up to date:
https://docs.google.com/document/d/1E2mkTHNQ5vyln1JvnJTil15cjacUTXP7LXb9K960Vxs/edit#heading=h.6k5h0aafbuyy
Here are the minutes:
DTS Working Group Meeting Minutes for 2022
January 19, 2022Attendees
-
Owen Hilyard
-
Lincoln Lavoie
-
Lijuan Tu
-
Juraj Linkes
-
Honnappa Nagarahalli
Agenda
-
Review/Carry forward pending action items
-
Merging DTS into DPDK
-
Review additional work items
MinutesReview/Carry forward pending action items
-
Honnappa - Propose changes to DPDK to address changing the constants and
printfs, refer to Lijuan’s email.
-
Work is started to add options for configuring the RX and TX queue
sizes for L3fwd sample application
-
Looking to remove the examples/distributor from DPDK which will end
up removing the corresponding test case from DTS.
-
Owen - Send out the DTS contributions guide to DTS and DPDK mailing
list. 2 weeks of RFC followed by a patch.
-
Email is sent
-
Owen, Lijuan - Look for merging the makefile removal patch (
http://patchwork.dpdk.org/project/dts/list/?series=20610)
-
No issues for CI
-
Add a depreciation warning for makefiles when run and in the release
notes
-
Honnappa - Understand how the SPDX change was done for the DPDK repo
-
State of an automated solution is unknown
-
We are legally ok to change files with BSD licenses and files with no
license to SPDX with BSD-3 clause
-
Honnappa - Talk to techboard about files with the GPL2 license in DTS.
-
Work in progress
-
Owen - Take a deeper look at the license and copyright assignments for
the files.
-
Completed
-
If there is a possibility of issues, a file-by-file examination would
be warranted
-
Juraj - Convert the makefile build for documentation to use meson build.
-
Juraj will look at this
DTS Contribution Guide
-
Integrate suggestions from Juraj
Merging DTS into DPDK
-
Try for 22.06
-
Focus on framework and test cases used in CI
-
pf_smoke
-
vf_smoke
-
virtio_smoke
-
nic_single_core_perf
-
mtu_update
-
stats_checks
-
dynamic_config
-
dynamic_queue
-
mac_filter
-
queue_start_stop
-
scatter
-
unit_tests_mbuf
Review additional work items
-
Action Items
-
Honnappa - Propose changes to DPDK to address changing the constants and
printfs, refer to Lijuan’s email.
-
All - Review Owen’s DTS contributions guide
-
Owen, Lijuan - Look for merging the makefile removal patch (
http://patchwork.dpdk.org/project/dts/list/?series=20610)
-
Honnappa - Understand how the SPDX change was done for the DPDK repo
-
Honnappa - Talk to techboard about files with the GPL2 license in DTS.
-
Juraj - Convert the makefile build for documentation to use meson build.
-
Owen - RFC for making the python version 3.6
-
Owen - Look at making DTS build using the DPDK repo it is in.
Any other business
-
Next Meeting: January 26, 2022
-
Subject for next meeting: Focus on getting framework ready to move
[-- Attachment #2: Type: text/html, Size: 33368 bytes --]
reply other threads:[~2022-01-26 15:07 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='CAHx6DYB8=+o+dg42TN_3R4oR3CuP6kCDruyGZ9d31ZS+-2e9HA@mail.gmail.com' \
--to=ohilyard@iol.unh.edu \
--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).