All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>
To: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.05-rc3
Date: Thu, 20 May 2021 13:04:19 +0530	[thread overview]
Message-ID: <CAH-L+nMxPHBWucHxQNJWKHNF_SQD0zNC5d1TAZN7FTmcxy0upA@mail.gmail.com> (raw)
In-Reply-To: <7142607.3L8AUzOtay@thomas>

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

All,

The following is a list of tests executed with 21.05-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 Thu, May 13, 2021 at 2:27 AM Thomas Monjalon <thomas@monjalon.net> wrote:

> A new DPDK release candidate is ready for testing:
>         https://git.dpdk.org/dpdk/tag/?id=v21.05-rc3
>
> There are 114 new patches in this snapshot.
>
> Release notes:
>         https://doc.dpdk.org/guides/rel_notes/release_21_05.html
>
> Please test and report issues on bugs.dpdk.org.
> You may share some release validation results
> by replying to this message at dev@dpdk.org.
>
> DPDK 21.05-rc4 will be out during next week for the final touch.
>
> Thank you everyone
>
>
>

-- 
Regards,
Kalesh A P

      parent reply	other threads:[~2021-05-20  7:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 20:57 [dpdk-dev] [dpdk-announce] release candidate 21.05-rc3 Thomas Monjalon
2021-05-14 10:07 ` Jiang, YuX
2021-05-18  7:29   ` Jiang, YuX
2021-05-19  4:07 ` Thinh Tran
2021-05-19 10:45 ` Ali Alnubani
2021-05-20  7:34 ` Kalesh Anakkur Purayil [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=CAH-L+nMxPHBWucHxQNJWKHNF_SQD0zNC5d1TAZN7FTmcxy0upA@mail.gmail.com \
    --to=kalesh-anakkur.purayil@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.