DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 25/02/2021
Date: Mon, 1 Mar 2021 02:57:31 +0000	[thread overview]
Message-ID: <AM5PR0802MB24652E2CC56178A47F20A58B9E9A9@AM5PR0802MB2465.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <78512871-3c33-7cdc-4653-10eb67df2d1a@intel.com>

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Ferruh Yigit
> Sent: Thursday, February 25, 2021 7:33 PM
> To: dev@dpdk.org
> Cc: thomas@monjalon.net
> Subject: [dpdk-dev] DPDK Release Status Meeting 25/02/2021
> 
> Meeting minutes of 25 February 2021
> -----------------------------------
> 
> Agenda:
> * Release Dates
> * Subtrees
> * LTS
> 
> Participants:
> * Arm
> * Broadcom
> * Debian/Microsoft
> * Intel
> * Marvell
> * Nvidia
> * Red Hat
> 
> 
> Release Dates
> -------------
> 
> * v21.05 dates
>    * Proposal/V1:    Thursday, 18 March
>    * -rc1:           Thursday, 15 April
>    * Release:        Friday, 14 May
> 
>    * Please send roadmaps, preferably before beginning of the release
>      * Thanks to Marvell and Huawei hns3 for sending roadmap
> 
> 
> Subtrees
> --------
> 
> * main
>    * Reviewing vfio patches from Nithin
>    * Alibaba's PIO patch is under review
>    * Power lib is causing build error
>      * New version required for the existing patch
>    * gcc11 build error, reproduced on fedora rawhide
>      * Issue is gone in newer version of gcc11, will wait for update
>    * Arm build issue
>      * Latest main doesn't fail anymore

I don't know if the issue on main is really resolved.
It happened when OBS job was scheduled to thunderxt88 hardware. The issue looks like compiler flag related.

>      * Centos 7 has different error
>        *
> https://build.opensuse.org/build/home:bluca:dpdk/CentOS_7/aarch64/dpd
> k/_log

Issue on CentOS 7 is because compiler being too old. 
Some log here:
[  173s] Compiler for C supports arguments -march=armv8.1-a+crc+crypto: NO
[  173s] Compiler for C supports arguments -mcpu=thunderx2t99: NO

This was discussed in earlier release status meeting. I think the conclusion was to ignore this failure.
https://mails.dpdk.org/archives/dev/2020-November/192374.html

>    * Thomas will send alpine & musl support
>      * This will affect all, please review
> 
> * next-net
>    * Consuming backlog, some patches already merged
> 
> * next-crypto
>    * The reviews are going on
> 
> * next-eventdev
>    * No update
> 
> * next-virtio
>    * No update
> 
> * next-net-mlx
>    * Some patches already merged, progressing
> 
> * next-net-brcm
>    * There is a set under review
> 
> * next-net-intel
>    * Some patches already merged, progressing
> 
> * next-net-mrvl
>    * No update
> 
> 
> LTS
> ---
> 
> * v19.11.7-rc1 is out, please test
>    *
> http://inbox.dpdk.org/dev/20210222155851.3002880-1-
> christian.ehrhardt@canonical.com/
> 
> * v20.11.1-rc1 is out, please test
>    * http://inbox.dpdk.org/dev/20210222150918.279483-1-
> luca.boccassi@gmail.com/
> 
> * For both of them target release date is March 8.
> 
> 
> 
> 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:[~2021-03-01  2:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 11:33 Ferruh Yigit
2021-03-01  2:57 ` Ruifeng Wang [this message]

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=AM5PR0802MB24652E2CC56178A47F20A58B9E9A9@AM5PR0802MB2465.eurprd08.prod.outlook.com \
    --to=ruifeng.wang@arm.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=nd@arm.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).