From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: dpdk-dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: release candidate 23.07-rc2
Date: Fri, 7 Jul 2023 04:18:56 -0500 [thread overview]
Message-ID: <6af7aadd-a793-ec86-aa5b-62c75be3a8ed@linux.vnet.ibm.com> (raw)
In-Reply-To: <2777875.6YUMPnJmAY@thomas>
IBM - Power Systems
DPDK v23.07-rc2-5-ga64a456470
* Build CI on Fedora 30,31,34,36,37 for ppc64le
* Basic PF on Mellanox: No issue found
* Performance: not tested.
* OS: RHEL 9.1 kernel: 5.14.0-162.6.1.el9_1.ppc64le
with gcc version 11.3.1 20220421 (Red Hat 11.3.1-2) (GCC)
RHEL 8.8 kernel: 4.18.0-477.10.1.el8_8.ppc64le
with gcc version 8.5.0 20210514 (Red Hat 8.5.0-18) (GCC)
Systems tested:
- LPARs on IBM Power10 CHRP IBM,9105-22A
NICs:
- Mellanox Mellanox Technologies MT2894 Family [ConnectX-6 Lx]
- firmware version: 26.37.1014
- MLNX_OFED_LINUX-23.04-0.5.3.6
Regards,
Thinh Tran
On 6/27/2023 7:59 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v23.07-rc2
>
> There are 237 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_23_07.html
>
> There were a lot of updates in drivers.
> The driver features should be frozen now.
>
> Please test and report issues on bugs.dpdk.org.
> Do not forget to review examples, tests and documentation updates.
> Breaking changes for 23.11 must be announced in 23.07.
>
> DPDK 23.07-rc3 is expected in approximately one week.
>
> Thank you everyone
>
>
>
>
>
prev parent reply other threads:[~2023-07-07 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 0:59 Thomas Monjalon
2023-06-29 6:49 ` Xu, HailinX
2023-07-06 6:43 ` Xu, HailinX
2023-07-07 9:18 ` 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=6af7aadd-a793-ec86-aa5b-62c75be3a8ed@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).