* [dpdk-dev] DPDK Release Status Meeting 15/10/2020
@ 2020-10-15 12:29 Ferruh Yigit
0 siblings, 0 replies; only message in thread
From: Ferruh Yigit @ 2020-10-15 12:29 UTC (permalink / raw)
To: dev; +Cc: Thomas Monjalon
Meeting minutes of 15 October 2020
----------------------------------
Agenda:
* Release Dates
* Subtrees
Participants:
* Arm
* Broadcom
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v20.11 dates
* -rc1: Friday, 16 October 2020
* -rc2: Friday, 30 October 2020
* Release: Friday, 13 November 2020
* Nvidia Mellanox, Marvell, Broadcom & Arm already sent roadmap, all
contributors please send roadmap for the release.
Subtrees
--------
* main
* Some patches won't able to make -rc1, there is no list on what won't make
* Some patches are stuck because they are waiting for response
* All authors please response/follow your patches
* There is a build issue needs immediate attention
https://bugs.dpdk.org/show_bug.cgi?id=556
* Power patches are in the queue, discussions going on
* Thomas has priority on ehtdev patches
* A new version of 'close()' set expected from Thomas
* Will pull form sub-trees
* Windows patches, most of them merged for the release
* -rc1 most probably will be out on Monday
* Ferruh will target to close next-net Friday evening
* More patches can be postponed to -rc2, even library ones, need to discuss
* Will keep release date as it is for now, will discuss it again
around the -rc2 timeline
* next-net
* Following ethdev patch reviews are going on, target is to get them for -rc1
* support VLAN attributes in ETH and VLAN items
* Rx buffer split
* New version sent today, there is a comment from Jerin after that
resolved we can proceed, may need a new version
* support for hairpin between two ports
* a new version sent this morning, Thomas is reviewing the set
* Tunnel Offload API
* There is an outstanding comment, need to resolve
* Requested for a rebased version, waiting for it
* rte_flow API thread safe
* since patchset has both eal and ethdev patch, it will be merged to main
* will review ethdev patch
* ethdev cleanup patches
* 'stop', 'close', xstats, unify returns, unify statics
* These all target for -rc1, but will be merges as last thing to
next-net to not cause conflict with existing ethdev patches
* Some are waiting for new versions
* Following ethdev patches will be postponed to next release
* capture hardware timestamps
* There are still issues to resolve for the patchset
* No version received yet, too late for -rc1
* use generic flow command to re-realize mirror rule
* received too late (yesterday), will consider for next release
* ethdev: add rx offload to drop error packets
* discussions are going on, no ack by maintainers, will postpone
* ethdev: support device reset and recovery events
* No ack from maintainers, waiting for response
* not clear what will happen if device can't recover
* ethdev: add security flow item
* There are arguments against it, will be rejected as it is
* txgbe PMD
* Overall looks good, planning to merge for release, minor changes requested
* Since above ethdev cleanup patches doesn't include this PMD, it will
conflict
* To prevent this conflict better to close ethdev patches in -rc1, and get
this PMD on -rc2 after rebased to latest ethdev changes.
* next-crypto
* Akhil prepared the pull request for the -rc1
* Two patches are not merged
* Security one and cryptodev one
* A cryptodev patch can be merged in -rc2, it is not ideal to merge library
changes after -rc1, but it can be discussed case by case.
* next-eventdev
* Jerin will prepare pull request today
* There are two new PMDs, two DLB driver versions
* Will wait eal and eventdev spec issues resolved in -rc1
* eal dependency is for the new CPU instructions
* Power changes are using those
* Will include Ruifeng from the Arm perspective
* The instructions are not supported by Arm, but good to check the
architecture
* Anyway new functions being experimental enables us fixing them later
* Will consider PMDs for -rc2
* next-virtio
* There is a fix in backlog can go in -rc2
* Arm NEON patch will be postponed for next release
* vhost add vectorized data path
* The improvement is small, may not worth the complexity it brings
* No go with current improvement level
* Add async datapath to vhost sample and optimize async datapath
* Under review
* Will get it for -rc1 if can make on time, else will be considered
for -rc2
* Some vhost security issues are still stuck in the security process
* Ferruh will be sure Maxime is involved into all, if not already
* next-net-intel
* There is new avf shared code as a major set
* There are other various PMD patches too, some can go in after -rc1
* next-net-mlx
* There are new series based on new ethdev features
* next-net-mrvl
* Ready for -rc1
* next-net-brcm
* There will be more patches for -rc2, after ethdev features merged for -rc1
* There are a few old patches in the backlog to take care
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 every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to
"John McNamara <john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-10-15 12:30 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-15 12:29 [dpdk-dev] DPDK Release Status Meeting 15/10/2020 Ferruh Yigit
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).