From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] Minutes of Technical Board Meeting, 2021-03-24
Date: Wed, 21 Apr 2021 10:50:00 +0000 [thread overview]
Message-ID: <SN7PR18MB4398FA346196FEDC46CB6D12C8479@SN7PR18MB4398.namprd18.prod.outlook.com> (raw)
Minutes of Technical Board Meeting, 2021-03-24
Members Attending
-----------------
-Bruce
-Ferruh
-Hemant
-Honnappa
-Jerin (Chair)
-Kevin
-Konstantin
-Maxime
-Olivier
-Stephen
-Thomas
NOTE: The technical board meetings 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-04-07 @3pm UTC, and will be chaired by Maxime
Build config options:
~~~~~~~~~~~~~~~~~~~~~
Immediate next steps:
1) Option to disable specific libraries
2) Moving driver config into driver directory
3) Option to reduce top-level configs
Long term:
1) Remove rte_config.h
2) Keep the top-level meson option as minimal or absolutely needed.
- Requested Bruce to sent RFC on
a) Configuring DPDK options
b) Documentation on additional options
Testing Leader's role documentation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- TB would like to have single point contact for testing efforts and prioritizing etc
- TB recommends Aaron to send an email in ml on
a) New role
b) information
c) Future plans
- Once the scope is agreed then host at dpdk.org's testing page
Vendor-specific examples:
~~~~~~~~~~~~~~~~~~~~~~~~~
1) NTB and IOAT raw driver's example application will be moved to example/drivers/raw/
to avoid PMD specific example application to show up examples directory.
2) Hemant volunteered to submit the patch for item (2) along with documentation policy
for the same.
reply other threads:[~2021-04-21 10:50 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=SN7PR18MB4398FA346196FEDC46CB6D12C8479@SN7PR18MB4398.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).