From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: dpdk-dev <dev@dpdk.org>
Subject: Re: release candidate 22.07-rc4
Date: Fri, 15 Jul 2022 09:18:37 -0500 [thread overview]
Message-ID: <29698c3f-5a69-9829-1f3c-f4694a5618f7@linux.vnet.ibm.com> (raw)
In-Reply-To: <6125682.jrt8l4j9yI@thomas>
IBM - Power Systems
DPDK v22.07-rc4-1-gb3c781dbde
* Basic PF on Mellanox: No new issues or regressions were seen.
* Performance: not tested.
* OS: RHEL 8.5 kernel: 4.18.0-372.9.1.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.33.1400
- MLNX_OFED_LINUX-5.6-1.0.3.6
- LPARs on IBM Power10 CHRP IBM,9105-22A
NICs:
- Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
- firmware version: 16.33.1400
- MLNX_OFED_LINUX-5.6-1.0.3.6
Regards,
Thinh Tran
On 7/11/2022 5:36 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v22.07-rc4
>
> There are 22 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_22_07.html
>
> This is the last release candidate.
> Only documentation should be updated before the release.
>
> Reviews of deprecation notices are required:
> https://patches.dpdk.org/bundle/dmarchand/deprecation_notices/
>
> 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.
>
> Please think about sharing your roadmap now for DPDK 22.11.
>
> Thank you everyone
>
>
next prev parent reply other threads:[~2022-07-15 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 22:36 Thomas Monjalon
2022-07-12 9:32 ` Jiang, YuX
2022-07-12 9:44 ` Xia, Chenbo
2022-07-14 8:17 ` Jiang, YuX
2022-07-15 7:59 ` Jiang, YuX
2022-07-15 14:18 ` Thinh Tran [this message]
2022-07-17 14:33 ` Wael Abualrub
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=29698c3f-5a69-9829-1f3c-f4694a5618f7@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 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).