From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: dpdk-dev <dev@dpdk.org>
Subject: Re: release candidate 22.03-rc3
Date: Sat, 12 Mar 2022 17:48:29 -0600 [thread overview]
Message-ID: <f0783673-52fd-e7c4-a214-86617d8a3bf2@linux.vnet.ibm.com> (raw)
In-Reply-To: <3941088.BzM5BlMlMQ@thomas>
Hi
IBM - Power Systems
DPDK v22.03-rc3-3-gca12f5e8a7
Tested with this patch [PATCH v2] net/mlx5: fix CPU socket ID for Rx
queue creation
* Basic PF on Mellanox: No new issues or regressions were seen.
* Performance: not tested.
Systems tested:
- IBM Power9 PowerNV 9006-22P
OS: RHEL 8.5
kernel: 4.18.0-348.7.1.el8_5.ppc64le
GCC: gcc version 8.5.0 20210514 (Red Hat 8.5.0-4)
NICs:
- Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
- firmware version: 16.29.1017
- MLNX_OFED_LINUX-5.2-1.0.4.1 (OFED-5.2-1.0.4)
- LPARs on IBM Power10 CHRP IBM,9105-22A
OS: RHEL 8.5
kernel: 4.18.0-348.el8.ppc64le
GCC: gcc version 8.5.0 20210514 (Red Hat 8.5.0-3)
NICs:
- Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
- firmware version: 16.32.1010
- MLNX_OFED_LINUX-5.5-1.0.3
Regards,
Thinh Tran
On 3/8/2022 5:43 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v22.03-rc3
>
> There are 102 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_22_03.html
>
> This should be the last release candidate.
> Only documentation and critical bug fixes are accepted until the release.
>
> Please test and report issues on bugs.dpdk.org.
> You may share some release validation results
> by replying to this message at dev@dpdk.org.
>
> Please think about sharing your roadmap now for DPDK 22.07.
>
> Thank you everyone
>
>
prev parent reply other threads:[~2022-03-12 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 23:43 release candidate 22.03-rc3 Thomas Monjalon
2022-03-10 8:57 ` Jiang, YuX
2022-03-14 11:46 ` Jiang, YuX
2022-03-10 13:33 ` Wael Abualrub
2022-03-12 23:48 ` Thinh Tran [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=f0783673-52fd-e7c4-a214-86617d8a3bf2@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.