DPDK patches and discussions
 help / color / mirror / Atom feed
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 2/04/2020
Date: Thu, 2 Apr 2020 18:48:17 +0100	[thread overview]
Message-ID: <473c31ca-9d99-b52d-a061-767276b00ac9@intel.com> (raw)

Minutes 2 April 2020
--------------------

Agenda:
* Release Dates
* Subtrees
* Opens

Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat


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

* v20.05 dates:
  * Integration/Merge/RC1:	Friday 17 April 2020
  * Release:			Wednesday 20 May 2020

  * Marvell, Arm, Mellanox & Broadcom already sent roadmap for 20.05, all
    vendors please share the roadmap for the release.


Subtrees
--------

* main
  * Reviewing trace series
  * Maybe merge crypto tree, next net will be merged after it
  * Call for review:
    http://inbox.dpdk.org/announce/10038126.3WhfQktd6Z@xps/T/#u
    * A prioritization done on that list:
      * Mandatory ones:
        * gcc 10 support
          * When DPDK 20.05 released, gcc10 will be default compiler for some

            distros
        * internal symbol marking
          * NXP will help making the patch
        * basic memory management for Windows
          * Expected to be merged in next a few weeks
      * High
        * cleanup more resources on shutdown
        * fixes and tests for rte_security
        * nodes graph as packet processing pipeline
        * telemetry rework
        * tracepoints compatible with LTTng
          * It is a useful feature, but affect a lot of parties,
            more review required
    * Please support by reviewing patches in this list (and more)

* next-net
  * Pulled from sub-trees and some patches merged
  * It is progressing, there are ~100 patches in backlog
  * There is a few big series and a new igc PMD

* next-crypto
  * No patches merged this week
  * Test for security API under review
  * bbdev, there were two patchset, one reviewed other in queue

* next-eventdev
  * Merging patches this week

* next-virtio
  * Maxime is off this week
  * Packed ring patches are under review
  * vhost example to use vhost PMD is under review
  * Using DMA engine in vhost example, after discussion it will be moved
    to library

* next-net-intel
  * Merged some shared code updates
  * Merged DCF
  * Several flow related patches merged
  * Maintainers are actively reviewing

* next-net-mlx
  * More patches to come, some RFC sent as text, working to make everything
    ready for -rc1

* LTS

  * 18.11.7-rc1 is out, please test
    * http://inbox.dpdk.org/dev/20200320193403.18959-1-ktraynor@redhat.com/
      * Red Hat & Intel sent test reports
    * Release planned for 14 April


Opens
-----

* Here comes DPDKoin. DPDKoin is a DPDK PMD, which instead of moving
  packets, mines cryptocurrencies.
  * http://inbox.dpdk.org/dev/20200401131044.7259-1-mcroce@redhat.com/#t



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-04-02 17:48 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=473c31ca-9d99-b52d-a061-767276b00ac9@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).