DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 5/11/2020
Date: Thu, 5 Nov 2020 12:42:15 +0000	[thread overview]
Message-ID: <365bd108-65dd-d76e-60af-914960bb2a5c@intel.com> (raw)

Meeting minutes of 5 November 2020
----------------------------------

Agenda:
* Release Dates
* Highlights
* -rc2 status
* Subtrees

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


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

* v20.11 dates
   * -rc2 is released on      Wednesday, 4 November 2020
     * http://inbox.dpdk.org/dev/2353813.dmDHS9aCqr@thomas/
   * -rc3 as quick fix is planned today, 5 November 2020
   * -rc4 pushed to           *Friday, 13 November 2020*
   * Release:                 Wednesday, 25 November 2020


Highlights
----------

* In -rc2 an issues has been found in the testpmd and a quick -rc3 is planned
   today with a hotfix.

   This will shift the numbering of the release candidates, previous -rc3 will
   now be -rc4, please do not confuse with this shift.


-rc2 status
-----------

* There is preliminary test result since -rc2 was only yesterday,
   * The testpmd issue (mentioned above) has been reported, which is blocking
     some set of tests.
     * The issue has been introduced in the commit:
       https://git.dpdk.org/dpdk/commit/?id=f6870a7ed6b3
       * Reverting this commit enables testing until the issue is addressed with
         a hotfix (and a possible quick new release candidate).


Subtrees
--------

* main
   * mbuf changes merged into the -rc2
     * some mbuf fields converted to dynamic field, for:
       * userdata fields (udata64)
       * sequence number field (seqn)
       * timestamp field (timestamp)
     * next step is to move mempool pointer to first cacheline
   * The mbuf changes done late in this release cycle, future mbuf
     related changes should be done as  community wise effort
   * There are issues in the language correction patchset
     * Although people agree to get it, there is not enough people
       doing the reviews.
       * Needed more detailed review for them
   * Discussed with Juraj about the status of Arm build option patchset
     * https://patches.dpdk.org/project/dpdk/list/?series=13572

* next-net
   * Nothing yet in the next-net after -rc2
   * Planning to get txgbe second set for next release candidate
     * After some requested fixes to initial set done
   * Will merge fixes after this point

* next-crypto
   * All patches merged for -rc2
   * enqueue & dequeue callbacks postponed to next release

* next-eventdev
   * DLB patches merged for -rc2
     * There were two drivers DLB/DLB2
       * HW is different but how big the difference is, can two PMDs combined
         into single PMD to reduce code clutter?
         * Will follow up with the author
   * There is no outstanding patches for now

* next-virtio
   * Nothing major left in the backlog
   * There will be fixes

* next-net-intel
   * No update

* next-net-mlx
   * More fixes in the backlog

* next-net-mrvl
   * No more patch expected

* next-net-brcm
   * A couple of features, no more feature


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.

                 reply	other threads:[~2020-11-05 12:42 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=365bd108-65dd-d76e-60af-914960bb2a5c@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).