patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: Ali Alnubani <alialnu@mellanox.com>
Cc: dpdk stable <stable@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	Olga Shern <olgas@mellanox.com>,
	Raslan Darawsheh <rasland@mellanox.com>
Subject: Re: [dpdk-stable] Mellanox's testing matrix for 17.11 LTS
Date: Mon, 15 Apr 2019 21:18:34 +0000	[thread overview]
Message-ID: <0C97E4BC-C616-41E2-B97A-BA1FD1362DDD@mellanox.com> (raw)
In-Reply-To: <AM6PR05MB44054C38A4A80E68DBB5F450D72B0@AM6PR05MB4405.eurprd05.prod.outlook.com>

Thanks you so much, Ali
Yongseok

> On Apr 15, 2019, at 9:51 AM, Ali Alnubani <alialnu@mellanox.com> wrote:
> 
> Hi Yongseok,
> 
> The following covers the tests that we ran on top of the 17.11 LTS branch:
>  
> •             Basic functionality:
> - Send and receive multiple types of traffic.
> - testpmd xstats counter test.
> - testpmd timestamp test.
> - Changing/checking link status through testpmd.
> •             RTE flow and flow_director tests.
> •             Some RSS tests.
> •             VLAN stripping and insertion tests.
> •             Checksum and TSO tests.
> •             ptype tests.
> •             Port interrupt testing.
> •             Multi-process testing.
>  
> Tests are passing, and we didn’t notice any issues.
>  
> Driver tested: rdma-core v23
>  
> Tested NICs:
> ConnectX-4 Lx (fw 14.24.1000).
> ConnectX-5 (fw 16.24.1000).
>  
> OSes tested:
> - Ubuntu 18.04.2 LTS (kernel 5.0.4-050004-generic).
> - RHEL7.4 (kernel 5.1.0-rc5).
> - RHEL7.5 (kernel 3.10.0-862.el7.x86_64).
>  
> Latest tested version:
> 3bed5d78d version: 17.11.6-rc1
> 
> Regards,
> Ali


      reply	other threads:[~2019-04-15 21:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 16:51 Ali Alnubani
2019-04-15 21:18 ` Yongseok Koh [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=0C97E4BC-C616-41E2-B97A-BA1FD1362DDD@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=alialnu@mellanox.com \
    --cc=olgas@mellanox.com \
    --cc=rasland@mellanox.com \
    --cc=stable@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).