DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pei Zhang <pezhang@redhat.com>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com, maxime.coquelin@redhat.com,
	qian.q.xu@intel.com,  ktraynor@redhat.com, thomas@monjalon.net,
	bluca@debian.org,  michael.j.glynn@intel.com,
	ferruh.yigit@intel.com,  christian.ehrhardt@canonical.com,
	olgas@mellanox.com,  mvarlese@suse.de, ian.stokes@intel.com,
	yskoh@mellanox.com,  techboard@dpdk.org, juzhang@redhat.com,
	siliu@redhat.com
Subject: [dpdk-dev] dpdk 18.11-rc3 testing results from Red Hat
Date: Fri, 16 Nov 2018 09:39:39 -0500 (EST)	[thread overview]
Message-ID: <519843175.44151082.1542379179625.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <167092742.44148156.1542378149549.JavaMail.zimbra@redhat.com>

Hi all, 

I'm Pei Zhang from Red Hat. We have tested dpdk 18.11-rc3 and we would like to share our testing results. 

Here are 10 testing scenarios we have covered and all get PASS result: 

(1)Guest with device assignment(PF) throughput testing(1G hugepage size) PASS 
(2)Guest with device assignment(PF) throughput testing(2M hugepage size) PASS 
(3)Guest with device assignment(VF) throughput testing PASS 
(4)PVP(host testpmd as vswitch) vhost-user 1Q throughput testing PASS 
(5)PVP(host testpmd as vswitch) vhost-user 2Q throughput testing PASS 
(6)PVP(host testpmd as vswitch) vhost-user 2Q & cross numa node throughput testing PASS 
(7)vhost-user reconnect with dpdk-client, qemu-server: ovs reconnect PASS 
(8)Guest with vhost-user hot plug throughput testing PASS 
(9)PVP(host testpmd as vswitch)vhost-user 1Q live migration testing PASS 
(10)Guest with ovs+dpdk+vhost-user single queue live migration testing PASS 

More testing details: 

Testing NICs: X540-AT2(ixgbe). 

Versions: 

Kernel: 3.10 

DPDK: 
http://dpdk.org/git/dpdk master 
commit 3e42b6ce06a1901b1ab631df4484ec8f548091c6 
Author: Thomas Monjalon <thomas@monjalon.net> 
Date: Wed Nov 14 05:05:29 2018 +0100 
version: 18.11-rc3 
Signed-off-by: Thomas Monjalon <thomas@monjalon.net> 

QEMU: 
git://git.qemu.org/qemu.git master 
commit cb968d275c145467c8b385a3618a207ec111eab1 
Author: Peter Maydell <peter.maydell@linaro.org> 
Date: Tue Nov 13 18:16:14 2018 +0000 
Update version for v3.1.0-rc1 release 
Signed-off-by: Peter Maydell <peter.maydell@linaro.org> 


Best regards, 
Pei Zhang 

       reply	other threads:[~2018-11-16 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167092742.44148156.1542378149549.JavaMail.zimbra@redhat.com>
2018-11-16 14:39 ` Pei Zhang [this message]
2018-11-26 15:11   ` [dpdk-dev] [PASS]dpdk 18.11-rc5 testing " Pei Zhang
2018-11-26 15:30     ` Thomas Monjalon

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=519843175.44151082.1542379179625.JavaMail.zimbra@redhat.com \
    --to=pezhang@redhat.com \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=ian.stokes@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=juzhang@redhat.com \
    --cc=ktraynor@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=michael.j.glynn@intel.com \
    --cc=mvarlese@suse.de \
    --cc=olgas@mellanox.com \
    --cc=qian.q.xu@intel.com \
    --cc=siliu@redhat.com \
    --cc=techboard@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=yskoh@mellanox.com \
    /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).