test suite reviews and discussions
 help / color / mirror / Atom feed
From: john miller <john.miller@atomicrules.com>
To: dts@dpdk.org
Subject: [dts] Minimum Tester/DUT configuration
Date: Wed, 14 Dec 2016 11:23:02 -0500	[thread overview]
Message-ID: <1FD3A933-F3E6-4B13-898D-A1B387B40345@atomicrules.com> (raw)


Hi All,

We have configured a tester and a DUT for DTS testing, both machines are 4 core systems, one running ubuntu 14.04 and the other ubuntu 16.04 OS's .  Before we plug our hardware into the tester we are trying to establish ground truth using a 2 port Fortville eagle card in the tester and one in the DUT.  The DTS documentation indicates that a minimum system requires 4 ports so my first question is, can some of the tests run with a 2 port configuration and is there any documentation that indicates which tests require all 4 ports ?   The basic tests like hello_world, timer, and cmdline pass, but when we attempt run tests like l2fwd we get the following error indicating that 4 ports are required.


                INFO: 
TEST SUITE : TestL2fwd
                INFO: NIC :        fortville_eagle
               ERROR: set_up_all failed:
Traceback (most recent call last):
  File "/work/dts/framework/test_case.py", line 223, in execute_setup_all
    self.set_up_all()
  File "/work/dts/tests/TestSuite_l2fwd.py", line 66, in set_up_all
    "Not enough ports for " + self.nic)
  File "/work/dts/framework/test_case.py", line 146, in verify
    raise VerifyFailure(description)
VerifyFailure: 'Not enough ports for fortville_eagle’



Also the DPDK mutilprocess test documentation indicates that the test should run with only 2 ports.  However when we attempt to run we get the following error.  The error looks like it is a result of the test attempting to use more lcores than are available on the DUT.  Although i could change the test script to avoid this, I would like to know if there is a configuration parameter that i missed that should be set to the number of cores on the DUT. 


         DTS_DUT_CMD: [192.168.0.11] ./examples/multi_process/simple_mp/simple_mp/x86_64-native-linuxapp-gcc/simple_mp -n 1 -c 0x6 --proc-type=primary
       SUITE_DUT_CMD: [192.168.0.11] ./examples/multi_process/simple_mp/simple_mp/x86_64-native-linuxapp-gcc/simple_mp -n 1 -c 0x60000 --proc-type=secondary
               ERROR: Test Case test_multiprocess_simple_mploadtest Result FAILED: TIMEOUT on ./examples/multi_process/simple_mp/simple_mp/x86_64-native-linuxapp-gcc/simple_mp -n 1 -c 0x60000 --proc-type=secondary
               ERROR: EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 0 on socket 0
EAL: Detected lcore 5 as core 1 on socket 0
EAL: Detected lcore 6 as core 2 on socket 0
EAL: Detected lcore 7 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 8 lcore(s)
EAL: lcore 17 unavailable
EAL: invalid coremask

Usage: ./examples/multi_process/simple_mp/simple_mp/x86_64-native-linuxapp-gcc/simple_mp [options]



Thank you,
-John

             reply	other threads:[~2016-12-14 16:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 16:23 john miller [this message]
2016-12-15 14:00 ` Liu, Yong
2017-01-24 16:10   ` john miller
2017-01-25  2:59     ` Liu, Yong
2017-01-25  3:08       ` john miller
2017-01-25  3:19         ` john miller
2017-01-25  5:25           ` Liu, Yong
2017-01-25  6:34             ` Xu, HuilongX
2017-01-27 13:33               ` john miller
2017-02-04  4: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=1FD3A933-F3E6-4B13-898D-A1B387B40345@atomicrules.com \
    --to=john.miller@atomicrules.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).