DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 2021-09-30
Date: Thu, 30 Sep 2021 19:59:20 +0000	[thread overview]
Message-ID: <SN6PR11MB30861C8CA78109D3B75CD4F6FCAA9@SN6PR11MB3086.namprd11.prod.outlook.com> (raw)

Release status meeting minutes 2021-09-30
=========================================

Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens

Participants:
* Broadcom
* Debian
* Intel
* Marvell
* Nvidia
* Red Hat


Release Dates
-------------

* v21.11 dates
  * Proposal/V1:    Friday, 10 September (complete)
  * -rc1:           Friday, 15 October
  * Release:        Friday, 19 November


Subtrees
--------

* next-net

  * Reviewing and merging ongoing
  * Pulled sub-trees and rebased to main
  * Will merge other subtrees today
  * Patch from ARM to fix descriptor order. However, there is a 20% decrease in performance on ThunderX. Other ARM vendors should check.
  * Release queue patch -  awaiting response

* next-net-intel

  - Waiting base code update
  - Tests need to be enabled in the  CI

* next-net-mlx

  - 3 patches merged and some merges ongoing
  - Big regex patchset will be merged directly to main

* next-net-brcm

  * Issue with GCC7 resolved

* next-net-mrvl

  - A lot of patches to merge
  - 2 big patches for inline-ipsec and ingress meter
  - https://patches.dpdk.org/project/dpdk/list/?series=18917&state=*

* next-eventdev

  * Intel patches merged (except one)
  * Changes on API hiding (for ABI stability) reviewed and looks  good.

* next-virtio

  * Still quite a few series under review
  * Fix for regression that could be merged: net/virtio: revert forcing IOVA as VA mode for virtio-user

* next-crypto

  * Progressing.
  * A few patches that can be merged
  * Issue with Windows CI failure

* main

  * **NOTE**: there are several large patchset on main the review detailed
    reviews from the community such as the series for Interrupts
    and for Thread API.
  * Merging experimental API updates ongoing
  * API updates for interrupts
    * Call to driver maintainers  to look at it:
    * https://patchwork.dpdk.org/project/dpdk/list/?series=18664
  * Some ASAN patches under review but need rework
  * Thread API series needs more reviews
    * https://patchwork.dpdk.org/project/dpdk/list/?series=18338
  * DMA device under review
  * Need to fix issue with MBUF segments
    * Should be merged this release and needs review
    * https://patches.dpdk.org/project/dpdk/patch/20210929213707.17727-1-olivier.matz@6wind.com/
  * Patches under test for automatic delegation patch delegation in the CI
  * Issue with KNI build on SuSE
  * New Slack channel: https://join.slack.com/t/dpdkproject/shared_invite/zt-v6c9ef5z-FqgOAS7BDAYqev_a~pbXdw




LTS
---

* v19.11 (next version is v19.11.10)
  * 20.11.3 released on Monday Sept 6

  * 19.11.10 released on Monday Sept 6



* Distros
  * v20.11 in Debian 11

  * v20.11 in Ubuntu 21.04




Defects
-------

* Bugzilla links, 'Bugs',  added for hosted projects
  - https://www.dpdk.org/hosted-projects/


Opens
-----

* Release of OpenSSL 3.0 will cause some compilation issues in cryptodev: https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/


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<mailto:john.mcnamara@intel.com>" for the invite.

                 reply	other threads:[~2021-09-30 19:59 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=SN6PR11MB30861C8CA78109D3B75CD4F6FCAA9@SN6PR11MB3086.namprd11.prod.outlook.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --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).