From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "M R, Chengappa (Network Function Virtualization)" <cm-r@hpe.com>,
"dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] low pass rate executing dts complete test suite
Date: Mon, 21 May 2018 13:49:07 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20EE094B8@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <TU4PR8401MB065404C07DFD82120E852EA999950@TU4PR8401MB0654.NAMPRD84.PROD.OUTLOOK.COM>
[-- Attachment #1.1: Type: text/plain, Size: 3707 bytes --]
Hi chengappa,
Here are my points:
1, the link might have some issues, such as link down
From the result "receive 0 , expect 64", I think , the link is down
You can check your link first before running dts.
2, DPDK will change during different version , so DTS will change with it.
Which DPDK and DTS 's version do you use?
From the failed result "set up failed" and timeout , I think your testpmd started failed.
Logs in output, you can check them to find the real reason, maybe testpmd's parameters changed.
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of M R, Chengappa (Network Function Virtualization)
Sent: Monday, May 21, 2018 7:28 PM
To: dts@dpdk.org
Subject: [dts] low pass rate executing dts complete test suite
Hello DTS community,
As we were investigation on DTS for Niantic (Intel Corporation 82599ES 10-Gigabit) platform and we are seeing very less pass rate.
We were under the assumption if we take care of the initial pre-requisites for TESTER and TARGET DUT as described here - https://dpdk.org/doc/dts/gsg/sys_reqs.html the DTS framework help us achieve a good pass rate.
Could you please help me by letting know if there are any fine tuning for the TARGET DUT so that I can see a better numbers than the current pass rate of 12.4%
[root@tester dts]# cat output/statistics.txt
Passed = 17
Failed = 45
Blocked = 68
Pass rate = 12.4
Some of the specification on the TARGET DUT and current running configuration are as follows
[root@targetdut ~]# lspci | egrep -i --color 'network|ethernet'
04:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Skyhawk) (rev 10)
04:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Skyhawk) (rev 10)
05:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
05:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
[root@tester dts]# cat conf/ports.cfg
# DUT Port Configuration
# [DUT IP]
# ports=
# pci=Pci BDF,intf=Kernel interface;
# pci=Pci BDF,mac=Mac address,peer=Tester Pci BDF,numa=Port Numa
# pci=Pci BDF,peer=IXIA:card.port
# pci=Pci BDF,peer=Tester Pci BDF,tp_ip=$(IP),tp_path=$({PERL_PATH);
# pci=Pci BDF,peer=Tester Pci BDF,sec_port=yes,first_port=Pci BDF;
# [VM NAME] virtual machine name; This section is for virutal scenario
# ports =
# dev_idx=device index of ports info, peer=Tester Pci BDF
[10.70.2.6]
ports =
pci=05:00.0,intf=ens2f0;
pci=05:00.1,intf=ens2f1;
[root@tester dts]# cat executions/execution.cfg
[Execution1]
crbs=10.70.2.6
drivername=igb_uio
test_suites=hello_world
test_suites=
cmdline,
hello_world
targets=x86_64-native-linuxapp-gcc
parameters=nic_type=niantic:func=true
[root@tester dts]# cat conf/crbs.cfg
#DUT crbs Configuration
#[DUT IP]
# dut_ip: DUT ip address
# dut_user: Login DUT username
# dut_passwd: Login DUT password
# os: operation system type linux or freebsd
# tester_ip: Tester ip address
# tester_passwd: Tester password
# ixia_group: IXIA group name
# channels: Board channel number
# bypass_core0: Whether by pass core0
[10.70.2.6]
dut_ip=10.70.2.6
dut_user=root
dut_passwd=HP1nvent
os=linux
tester_ip=10.70.2.5
tester_passwd=HP1nvent
channels=4
Snippet of the current results
[cid:image001.png@01D3F14B.FBB523F0]
[cid:image002.png@01D3F14B.FBB523F0]
[cid:image003.png@01D3F14B.FBB523F0]
[cid:image004.png@01D3F14B.FBB523F0]
Thanking in advance,
Chengappa
If everyone is moving forward together, then success takes care of itself....!!
[-- Attachment #1.2: Type: text/html, Size: 21083 bytes --]
[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 75429 bytes --]
[-- Attachment #3: image002.png --]
[-- Type: image/png, Size: 90260 bytes --]
[-- Attachment #4: image003.png --]
[-- Type: image/png, Size: 94096 bytes --]
[-- Attachment #5: image004.png --]
[-- Type: image/png, Size: 85027 bytes --]
next prev parent reply other threads:[~2018-05-21 13:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 11:28 M R, Chengappa (Network Function Virtualization)
2018-05-21 13:49 ` Tu, Lijuan [this message]
2018-05-22 1:42 ` Xu, GangX
2018-05-22 2:57 ` M R, Chengappa (Network Function Virtualization)
2018-05-22 6:57 ` Tu, Lijuan
2018-06-01 10:16 ` M R, Chengappa (Network Function Virtualization)
2018-06-08 8:20 ` Liu, Yong
2018-06-08 8:40 ` M R, Chengappa (Network Function Virtualization)
2018-06-10 14:27 ` Liu, Yong
2018-06-10 16:12 ` M R, Chengappa (Network Function Virtualization)
2018-06-11 6:41 ` Xu, GangX
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=8CE3E05A3F976642AAB0F4675D0AD20EE094B8@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=cm-r@hpe.com \
--cc=dts@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 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).