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, 2019-11-06
Date: Wed, 20 Nov 2019 05:26:05 +0000 [thread overview]
Message-ID: <BYAPR18MB2424CD497704EABBA69C08FDC84F0@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
Minutes of Technical Board Meeting, 2019-11-06
Members Attending
-----------------
-Bruce
-Ferruh
-Hemant
-Honnappa
-Jerin (Chair)
-Kevin
-Konstantin
-Maxime
-Olivier
-Thomas
NOTE: The technical board meetings every second Wednesday on IRC channel #dpdk-board, at 3pm UTC. Meetings are public and DPDK community members are welcome to attend.
NOTE: Next meeting will be on Wednesday 2019-11-20 @3pm UTC, and will be chaired by Honnappa
1) ABI policy review
- Reviewed API policy (http://inbox.dpdk.org/dev/2325188.Q6BSOo8498@xps/T/#u)
- Thomas sent the techboard's feedback on the mailing list
http://mails.dpdk.org/archives/dev/2019-November/150468.html
2) cpu-crypto API choices (http://patches.dpdk.org/cover/62489/)
- Decided to form a subgroup (Konstantin, Akhil, Honnappa, Hemant, Anoob, Jerin) for the discussion
- If there is no a clear majority then come back to the techboard for next level of discussions.
- Option provided to have reserved field in the public data structures to avoid ABI break for
future releases.
3) vfio-pf out of tree module discussion follow-up
Following has been decided
- Disable all kmods in 20.02 by default
- Move igb_uio kernel module to new repo hosted by dpdk.org in v20.11
- The kernel VFIO maintainer thinks there _can_ be a solution for the DPDK use case.
Action item to send the kernel patch and discuss with kernel community.
Now, vfio_pf patch-set put on hold. It will not be not merged in v19.11 release.
4) VF port representor ops to ethdev (http://patches.dpdk.org/patch/62176/)
For the benefit of existing application and driver which implemented this API,
It's been decided to follow the existing logic. i.e. No change in ethdev API for
V19.11 release.
reply other threads:[~2019-11-20 5:26 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=BYAPR18MB2424CD497704EABBA69C08FDC84F0@BYAPR18MB2424.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).