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: DPDK Release Candidate 24.11-rc3 Testing Report
Date: Tue, 26 Nov 2024 13:21:54 +0000 [thread overview]
Message-ID: <MW4PR12MB86118D4554972D24486C2B58D62F2@MW4PR12MB8611.namprd12.prod.outlook.com> (raw)
In-Reply-To: <17154210.Ash8RoxBsO@thomas>
Hi,
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, November 20, 2024 4:13 AM
> To: announce@dpdk.org
> Subject: release candidate 24.11-rc3
>
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v24.11-rc3
>
> There are 192 new patches in this snapshot.
> Hopefully almost everything expected should be in.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_24_11.html
>
> Highlights of 24.11-rc3:
> - Realtek r8169 net driver
> - ZTE gdtc raw driver
>
> As usual, you can report any issue on https://bugs.dpdk.org
>
> Only documentation and critical bug fixes should be accepted at this stage.
>
> There are only 10 days remaining before the end of the month.
> DPDK 24.11-rc4 should be the last release candidate (in one week).
>
> Thank you everyone
>
The following is the testing report for 24.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:
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
next prev parent reply other threads:[~2024-11-26 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 2:12 release candidate 24.11-rc3 Thomas Monjalon
2024-11-21 9:32 ` r8169 throughput Howard Wang
2024-11-21 10:33 ` Thomas Monjalon
2024-11-22 2:29 ` 答复: " 王颢
2024-11-26 13:21 ` Wael Abualrub [this message]
2024-11-26 17:14 ` release candidate 24.11-rc3 Thinh Tran
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=MW4PR12MB86118D4554972D24486C2B58D62F2@MW4PR12MB8611.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).