From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 4/06/2020
Date: Thu, 4 Jun 2020 11:12:25 +0100 [thread overview]
Message-ID: <de9a185b-8f91-4482-8c99-9a1133f59730@intel.com> (raw)
Minutes 4 June 2020
-------------------
Agenda:
* Meeting
* Release Dates
* Subtrees
* OvS
Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat
Meeting
-------
* It has been discussed to use different meeting infrastructure in the
retrospective meeting.
* https://mails.dpdk.org/archives/dev/2020-May/168971.html
* There was no update so continued with Skype on this meeting
* Jitsi suggested, an update will be announced for next meeting
Release Dates
-------------
* v20.08 dates:
* Proposal/V1: Friday, 12 June 2020
* -rc1: Wednesday, 8 July 2020
* -rc2: Monday, 20 July 2020
* Release: Tuesday, 4 August 2020
* Red Hat, Mellanox & Marvell already sent roadmap, all contributors please
send roadmap for the release.
Subtrees
--------
* main
* There is new interrupt maintainer, thanks Harman for volunteering
https://patches.dpdk.org/patch/70846/
* VF Token patch can be merged soon
v15: https://patches.dpdk.org/project/dpdk/list/?series=10272
* Kernel support in 5.6
* Should be tested
* Will merge some windows patches
* Like memory management wrappers, that affect all
* Will plan an merge from next-net tomorrow
* Roadmap update
* Will send a patch to update roadmap webpage
* Will update roadmap with agreed changes, like moving igb_uoi
* Roadmap is missing from Intel and Arm
* Call for review for two flow API changes
* [RFC] add flow action context API (https://patches.dpdk.org/patch/70465/)
* "Flow API sampling/mirroring action", not sent yet
* next-net
* Merged some patches and pulled from sub-trees
* Around 50 patch majority from previous release
* Enough commits accumulated for an early merge
* next-crypto
* No update this week, will start reviews this week
* next-eventdev
* A few patches waiting review
* next-virtio
* A few series to review, will start review
* next-net-mrvl
* Will start merging next week
LTS
---
* v19.11.3-rc1 is out, please test
* https://mails.dpdk.org/archives/dev/2020-June/169263.html
* Release is planned tentatively two weeks later (17 June)
* Vendors need to secure the testing resource for the LTS
* v18.11.9 in progress
* Halfway through the backport
* Planning to have an -rc and of next week
OvS
---
* Validating CVE fixes
* A performance drop observed in vhost, can share the result
* Need to check/verify this performance drop in DPDK
* Release feature deadline is beginning of the July and code freeze on mid July
* Working on vxlan offload and vxlan TSO with Mellanox and Broadcom
* The solution may end up being in DPDK instead of OvS
* CPU instruction enablement is going on for Intel
DPDK Release Status Meetings
============================
The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
reply other threads:[~2020-06-04 10:12 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=de9a185b-8f91-4482-8c99-9a1133f59730@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).