test suite reviews and discussions
 help / color / mirror / Atom feed
From: Kevin Wilson <wkevils@gmail.com>
To: dts@dpdk.org
Subject: [dts] L2FW fails with 'Not enough cores for performance!!!' (framework/etgen, py)
Date: Mon, 16 Apr 2018 14:46:34 +0300	[thread overview]
Message-ID: <CAGXs5wU3z158RUm50h1j+isFno7f1i8vED__8XXvN+BfLzqR8Q@mail.gmail.com> (raw)

Hi,
I am trying to run DTS L2FW performance between a tester and a DUT using DTS
(with scapy, not with IXIA) and I am getting the following error:
TestL2fwd: Test Case test_perf_l2fwd_performance Result FAILED: 'Not
enough cores for performance!!!'
and the DTS app terminates.
I located the error, and it is from packet_generator() method of
framework/etgen.py
What can be the reason for this  ?

Further details:
The execution.cfg file I am using is:
[Execution1]
crbs=IP adderss of DUT
drivername=igb_uio
test_suites=
       l2fwd
targets=
    x86_64-native-linuxapp-gcc
parameters=nic_type=niantic:perf=true

I have 2 machine: host A is the tester, and host B is the DUT.
Both have IXGBE nics, and each of these 2 nics have 2 ports.
On the tester, the PCI ids of the IXGBEs are 0000:04:00.0 and 0000:04:00.1
On the DUT, the PCI ids of the IXGBEs are 0000:06:00.0 and 0000:06:00.1
The IXGBEs are 8086:158b on both hosts

I have two configuration files:
conf/ports.cfg:
[DUT IP]
ports =
    pci=0000:06:00.0,peer=0000:04:00.0;
    pci=0000:06:00.1,peer=0000:04:00.1;


conf/crb.cfg:

[DUT IP]
dut_ip=DUT IP
dut_user=root
dut_passwd=dut_password
os=linux
tester_ip=TESTER IP
tester_passwd=tester_password
channels=4
bypass_core0=False

Both hosts have 4 cores (as is shown by "cat /proc/cpuinfo | grep -i processor")
I am running DTS by:
./dts --git=v17.11  --config-file=myConfig.cfg


Regards,
Kevin

             reply	other threads:[~2018-04-16 11:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 11:46 Kevin Wilson [this message]
2018-04-17  1:34 ` Liu, Yong
2018-04-17 18:52   ` Kevin Wilson
2018-04-18  2:18     ` Liu, Yong
2018-04-18 18:10       ` Kevin Wilson
2018-04-19  6:02         ` Liu, Yong

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=CAGXs5wU3z158RUm50h1j+isFno7f1i8vED__8XXvN+BfLzqR8Q@mail.gmail.com \
    --to=wkevils@gmail.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).