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: Raslan Darawsheh <rasland@nvidia.com>,
	Ali Alnubani <alialnu@nvidia.com>,  "dev@dpdk.org" <dev@dpdk.org>
Subject: testing report for DPDK release candidate 23.11-rc3
Date: Thu, 23 Nov 2023 08:21:57 +0000	[thread overview]
Message-ID: <PH7PR12MB9222C6D0DC80C137DF49473CD6B9A@PH7PR12MB9222.namprd12.prod.outlook.com> (raw)
In-Reply-To: <6817568.e9J7NaK4W3@thomas>

Hi,

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, November 15, 2023 12:01 AM
> To: announce@dpdk.org
> Subject: release candidate 23.11-rc3
>
> 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
>

The following is the testing report for 23.11-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:[~2023-11-23  8:22 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
2023-11-23  8:21 ` Wael Abualrub [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=PH7PR12MB9222C6D0DC80C137DF49473CD6B9A@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).