From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>
Subject: Re: release candidate 22.11-rc3
Date: Mon, 21 Nov 2022 14:22:02 -0600 [thread overview]
Message-ID: <df38dd38-f68e-c2d8-7dab-c604667f4e81@linux.vnet.ibm.com> (raw)
In-Reply-To: <1720725.X513TT2pbd@thomas>
IBM - Power Systems
DPDK 22.11.0-rc3
* Basic PF on Mellanox: No new issues or regressions were seen.
* Performance: not tested.
* OS: RHEL 8.5 kernel: 4.18.0-348.el8.ppc64le
with gcc version 8.5.0 20210514 (Red Hat 8.5.0-10)
RHEL 9.0 kernel: 5.14.0-70.13.1.el9_0.ppc64le
with gcc version 11.2.1 20220127 (Red Hat 11.2.1-9)
Systems tested:
- IBM Power9 PowerNV 9006-22P
NICs:
- Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
- firmware version: 16.34.1002
- MLNX_OFED_LINUX-5.7-1.0.2.1 (OFED-5.7-1.0.2)
- IBM Power10 PowerVM IBM,9105-22A
NICs:
- Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
- firmware version: 16.34.1002
- MLNX_OFED_LINUX-5.7-1.0.2.1 (OFED-5.7-1.0.2)
Regards,
Thinh Tran
On 11/15/2022 11:32 AM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v22.11-rc3
>
> There are 161 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_22_11.html
>
> 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
> and by adding tested hardware in the release notes.
>
> DPDK 22.11-rc4 should be the last chance for bug fixes and doc updates,
> and it is planned for the end of this week.
>
> Thank you everyone
>
>
prev parent reply other threads:[~2022-11-21 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 17:32 Thomas Monjalon
2022-11-17 8:20 ` David Marchand
2022-11-17 8:48 ` Jiang, YuX
2022-11-21 13:50 ` Jiang, YuX
2022-11-21 14:13 ` Ferruh Yigit
2022-11-22 10:17 ` Jiang, YuX
2022-11-20 15:47 ` Wael Abualrub
2022-11-21 20:22 ` 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=df38dd38-f68e-c2d8-7dab-c604667f4e81@linux.vnet.ibm.com \
--to=thinhtr@linux.vnet.ibm.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).