DPDK patches and discussions
 help / color / mirror / Atom feed
From: Wael Abualrub <waela@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Ali Alnubani <alialnu@nvidia.com>
Subject: Testing report for DPDK release candidate 24.03-rc3
Date: Mon, 25 Mar 2024 07:33:47 +0000	[thread overview]
Message-ID: <PH7PR12MB9222FC06EAF54339354BE720D6362@PH7PR12MB9222.namprd12.prod.outlook.com> (raw)
In-Reply-To: <3273963.N7aMVyhfb1@thomas>

Hi,

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Monday, March 18, 2024 5:46 AM
> To: announce@dpdk.org
> Subject: release candidate 24.03-rc3
>
> 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
>

The following is the testing report for 24.03-rc3.

Note: all tests are passed, and no critical issues were found.

The following is a list of tests that we ran on NVIDIA hardware this release:

- Basic functionality:
   Send and receive multiple types of traffic.
- testpmd xstats counter test.
- testpmd timestamp test.
- Changing/checking link status through testpmd.

- RTE flow tests:
 See: https://doc.dpdk.org/guides/nics/mlx5.html#supported-hardware-offloads

- RSS testing.
- VLAN filtering, stripping and insertion tests.
- Checksum and TSO tests.
- ptype reporting.
- link status interrupt using the example application link_status_interrupt tests.
- Interrupt mode using l3fwd-power example application tests.
- Multi process testing using multi process example applications.
- Hardware LRO tests.
- Regex tests.
- Buffer Split.
- Tx scheduling.

Kindest Regards,
Wael Abualrub

  parent reply	other threads:[~2024-03-25  7:33 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
2024-03-25  7:33 ` Wael Abualrub [this message]
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=PH7PR12MB9222FC06EAF54339354BE720D6362@PH7PR12MB9222.namprd12.prod.outlook.com \
    --to=waela@nvidia.com \
    --cc=alialnu@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=rasland@nvidia.com \
    --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).