From: Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>
To: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.08-rc3
Date: Tue, 3 Aug 2021 11:04:39 +0530 [thread overview]
Message-ID: <CAH-L+nOAxcdSEQpRmm3otc4QjMJtKvJV2mqtteGZgMeZg9AL9Q@mail.gmail.com> (raw)
In-Reply-To: <2121763.s2ZnmXpLtD@thomas>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
Hi Thomas,
The testing with dpdk 21.08-rc3 from Broadcom looks good. The following is
a list of tests executed with 21.08-rc3:
- Basic functionality:
Send and receive multiple types of traffic.
- testpmd xstats counter test.
- RSS tests.
- VLAN filtering tests.
- Rx Checksum tests
- TSO tests.
- MTU and Jumbo frame tests
- Changing/checking link status through testpmd.
- Unicast/multicast MAC filtering tests
- VXLAN/Geneve Rx CSO, TSO, RSS tests
We don't see any critical issues blocking the release.
Regards,
Kalesh
On Sun, Aug 1, 2021 at 2:49 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v21.08-rc3
>
> There are 70 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_21_08.html
>
> Please check all pending announces of deprecations for 21.11.
> https://patches.dpdk.org/project/dpdk/list/?q=announce
>
> You may share some release validation results
> by replying to this message at dev@dpdk.org.
>
> DPDK 21.08-rc4 is expected on Wednesday.
>
> Thank you everyone
>
>
>
--
Regards,
Kalesh A P
next prev parent reply other threads:[~2021-08-03 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 21:19 Thomas Monjalon
2021-08-03 5:34 ` Kalesh Anakkur Purayil [this message]
2021-08-03 17:36 ` Thinh Tran
2021-08-04 11:38 ` Jiang, YuX
2021-08-04 12:48 ` Thomas Monjalon
2021-08-05 10:35 ` Jiang, YuX
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=CAH-L+nOAxcdSEQpRmm3otc4QjMJtKvJV2mqtteGZgMeZg9AL9Q@mail.gmail.com \
--to=kalesh-anakkur.purayil@broadcom.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).