From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: DPDK Techboard <techboard@dpdk.org>
Subject: [dpdk-dev] [dpdk-techboard] Minutes of Technical Board Meeting, 2021-04-21
Date: Tue, 27 Apr 2021 15:07:26 +0000 [thread overview]
Message-ID: <DM6PR11MB4491419EB4D2E620BAEF78FE9A419@DM6PR11MB4491.namprd11.prod.outlook.com> (raw)
Minutes of Technical Board Meeting, 2021-04-21
Members Attending
---------------------------
-Aaron
-Bruce
-Ferruh
-Hemant
-Honnappa
-Jerin
-Kevin
-Konstantin (chair)
-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-21 @3pm UTC, and will be
chaired by Kevin.
1) eventdev DLB2 -> DLB driver rename
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* it could be considered as API/ABI breakage, so should happen at LTS release timeframe (21.11)
* Renaming it back to DLB is possible, but might create a confusion,
when 20.11 LTS and 21.11 LTS will have two different drivers with the same name (dlb).
* Proposal to consider to use new name (idlb) for renaming in 21.11.
2) build: use platform option 'generic' as default one
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Current default option is 'native'.
* To go ahead with such noticeable change need to collect feedback from the community first.
* Techboard preference is to keep 'native' as a default choice.
3) Tech Board Membership Policy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Agreed that it needs to be clearly defined and better documented.
* Start with codifying current status (AR to Hemant).
* Review existing policies for other open-source projects and come-up
with some suitable proposal for DPDK (AR to Stephen and other members).
4) Linux Foundation interaction
~~~~~~~~~~~~~~~~~~~~~~~~~~
Discussion on current situation and what can be improved in future.
5) DPDK Userspace 2021
~~~~~~~~~~~~~~~~~~~~
Discussed initial thoughts about DPDK Userspace 2021 event.
Techboard opinion:
In current situation it seems premature to consider F2F event for 2021.
Probably safer to plan it as virtual for 2021 and consider F2F one for 2022.
6) Other opens
~~~~~~~~~~~~~
* More reviews for 21.05 are welcome (as usual)
* examples/l3fwd - looking for maintainer.
reply other threads:[~2021-04-27 15:08 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=DM6PR11MB4491419EB4D2E620BAEF78FE9A419@DM6PR11MB4491.namprd11.prod.outlook.com \
--to=konstantin.ananyev@intel.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).