From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Minutes of Technical Board Meeting - 2022-April-06
Date: Tue, 19 Apr 2022 05:07:42 +0000 [thread overview]
Message-ID: <BY3PR18MB4785E42225D8BAD50A54DEF0C8F29@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
Minutes of Technical Board Meeting, 2022-April-06
Members Attending
-----------------
-Aaron
-Bruce
-Ferruh
-Hemant
-Honnappa
-Jerin (Chair)
-Kevin
-Konstantin
-Maxime
-Olivier
-Stephen
-Thomas
NOTE: The technical board meetings are on every second Wednesday at https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
NOTE: Next meeting will be on Wednesday 2021-April-20 @3pm UTC, and will be chaired by Konstantin.
1) Update on UNH SOW
---------------------
# TB approved UNH SOW by voting.
2) Userspace event
-------------------
# Discussed various aspects of event planning. No specific plan is finalized.
# Thomas to start TB email thread for planning the 3 days event to decide activity breakup.
3) PMD API
---------------------
# In general, PMD specific APIs are not recommended and they can be considered for the inclusion in the DPDK repository when
the contributor is convinced that a specific feature that is part of PMD can not make as generic.
If so, as a first step, the contributor sends an email to the DPDK mailing list CCing relevant maintainers to
explain the use case with PMD API prototype and data model as RFC.
# If community/maintainers decide it can not become generic API or the RFC lacks review/interest on RFC, then contributor
can go with PMD-specific API.
# New PMD-specific APIs are not allowed to add in testpmd or another generic DPDK application inside the DPDK repository.
# To verify the functionalities of PMD API, The testpmd needs to be updated to use a new plugin model,
where, the new additions must be done in driver/subsystem/driver_name/ path by changing the minimum
common testpmd code as possible.
4) TB Membership update
------------------------
# Ferruh resigned from TB. At this point, TB is not open for new TB membership.
reply other threads:[~2022-04-19 5: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=BY3PR18MB4785E42225D8BAD50A54DEF0C8F29@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=techboard@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).