From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.02-rc2
Date: Thu, 4 Feb 2021 14:07:24 -0800 [thread overview]
Message-ID: <2c8bd0f0-8dec-4d84-e7b2-e73cddfd975f@linux.vnet.ibm.com> (raw)
In-Reply-To: <2701263.OCiMXv1sLx@thomas>
DPDK 21.02 on IBM Power result
* DPDK: v21.02-rc2-5-gf6f2d2240
* Build with gcc 9.3.0-1: no issue found
* Basic PF on Mallanox: No new issues or regressions were seen.
* Performance: not tested yet.
System tested:
- IBM Power9 Model 8335-101 CPU: 2.3 (pvr 004e 1203)
Tested NICs:
- Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
- MLNX_OFED_LINUX-5.2-1.0.4.1
- Firmware level: 16.29.1016
Regards,
Thinh Tran
On 1/29/2021 5:23 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v21.02-rc2
>
> There are 293 new patches in this snapshot,
> more than expected for a light release cycle.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_21_02.html
>
> Highlights of 21.02-rc2:
> - new pmdinfogen with Windows support
> - power management for core polling single ethdev queue
> - Marvell OCTEON TX EP net PMD
> - Mellanox compress PMD
> - Virtio PMD rework
>
> Please test and report issues on bugs.dpdk.org.
>
> The -rc3 should include only some bug fixes, cleanups, doc and tooling.
>
> Next Thursday (February 4) should be the day of closing 21.02-rc3.
> The goal is to complete the release before the Chinese New Year
> to allow a quiet rest during the Spring Festival.
>
> Thank you everyone
>
>
next prev parent reply other threads:[~2021-02-04 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 1:23 [dpdk-dev] [dpdk-announce] release candidate 21.02-rc2 Thomas Monjalon
2021-02-01 9:49 ` Jiang, YuX
2021-02-04 5:12 ` Jiang, YuX
2021-02-04 22:07 ` Thinh Tran [this message]
2021-02-07 12:59 ` Pei Zhang
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=2c8bd0f0-8dec-4d84-e7b2-e73cddfd975f@linux.vnet.ibm.com \
--to=thinhtr@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.