From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: release candidate 23.11-rc3
Date: Mon, 20 Nov 2023 11:32:06 -0600 [thread overview]
Message-ID: <2760f6ec-ba44-466e-9625-3fcd6605c3af@linux.vnet.ibm.com> (raw)
In-Reply-To: <6817568.e9J7NaK4W3@thomas>
Hi,
IBM - Power Systems
DPDK v23.11-rc3-2-g6d7129a6e9
* Build CI on Fedora 30,31,34,36,37,38 for ppc64le
* Basic PF on Mellanox: No issue found
* Performance: not tested.
* OS: RHEL 9.2 kernel: 5.14.0-284.25.1.el9_2.ppc64le
with gcc version 11.3.1 20221121 (Red Hat 11.3.1-4) (GCC)
RHEL 8.6 kernel: 4.18.0-348.el8.ppc64le
with gcc version 8.5.0 20210514 (Red Hat 8.5.0-10) (GCC)
Systems tested:
- LPARs on IBM Power10 CHRP IBM,9105-22A
NICs:
- Mellanox Mellanox Technologies MT2894 Family [ConnectX-6 Lx]
- firmware version: 26.38.1002
- MMLNX_OFED_LINUX-23.07-0.5.0.2
Thanks,
Thinh Tran
On 11/14/2023 4:00 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v23.11-rc3
>
> There are 129 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_23_11.html
>
> Please test and report issues on bugs.dpdk.org.
>
> Only doc, tools, and bug fixes should be accepted at this stage.
>
> DPDK 23.11-rc4 should be the last release candidate.
> The final release should be done before the end of next week.
>
> Thank you everyone
>
>
next prev parent reply other threads:[~2023-11-20 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 22:00 Thomas Monjalon
2023-11-16 9:10 ` Xu, HailinX
2023-11-21 11:26 ` Xu, HailinX
2023-11-22 5:41 ` Xu, HailinX
2023-11-22 10:26 ` Ferruh Yigit
2023-11-23 1:33 ` Xu, HailinX
2023-11-20 17:32 ` Thinh Tran [this message]
2023-11-23 8:21 ` testing report for DPDK " 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=2760f6ec-ba44-466e-9625-3fcd6605c3af@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).