DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thinh Tran <thinhtr@linux.ibm.com>
To: dpdk-dev <dev@dpdk.org>
Subject: Re: release candidate 24.03-rc3
Date: Fri, 22 Mar 2024 13:41:29 -0500	[thread overview]
Message-ID: <f0743aae-c9cb-4e31-a350-9cbcb15ef011@linux.ibm.com> (raw)
In-Reply-To: <3273963.N7aMVyhfb1@thomas>

IBM - Power Systems
DPDK v24.03-rc3-2-gc96e9ca312


* Build CI on Fedora 30,37,38,39,40 container images for ppc64le
* Basic PF on Mellanox: No issue found
* Performance: not tested.
* OS:- RHEL 9.3  kernel: 5.14.0-362.2.1.el9_3.ppc64le
         with gcc version 11.4.1 20230605 (Red Hat 11.4.1-2)
      - RHEL 9.2  kernel: 5.14.0-284.52.1.el9_2.ppc64le
         with gcc version 11.3.1 20221121 (Red Hat 11.3.1-4) (GCC)

      - SLES 15-SP5 ppc64le kernel: 5.14.21-150500.55.44-default
     with gcc version 12.3.0 (SUSE Linux)

Systems tested:
  - LPARs on IBM Power10 CHRP IBM,9105-22A
     NICs:
     - Mellanox Mellanox Technologies MT2894 Family [ConnectX-6 Lx]
     - firmware version: 26.40.1000
     - MLNX_OFED_LINUX-24.01-0.3.3.5


Regards,
Thinh Tran


On 3/17/2024 10:45 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v24.03-rc3
> 
> There are 153 new patches in this snapshot.
> 
> Release notes:
> 	https://doc.dpdk.org/guides/rel_notes/release_24_03.html
> 
> As usual, you can report any issue on https://bugs.dpdk.org
> 
> Only documentation and bug fixes should be accepted at this stage.
> 
> DPDK 24.03-rc4 should be the last release candidate.
> The final release should be done on 27th if no surprise.
> 
> Thank you everyone
> 
> 

  reply	other threads:[~2024-03-22 18:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18  3:45 Thomas Monjalon
2024-03-22 18:41 ` Thinh Tran [this message]
2024-03-25  7:33 ` Testing report for DPDK " Wael Abualrub
2024-03-26  8:30 ` Xu, HailinX

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=f0743aae-c9cb-4e31-a350-9cbcb15ef011@linux.ibm.com \
    --to=thinhtr@linux.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).