DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Liu <dliu@iol.unh.edu>
To: "Tu, Lijuan" <lijuan.tu@intel.com>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] DTS Test Nic Single Core Perf Scapy Naming Conflict
Date: Thu, 19 Nov 2020 14:34:08 -0500	[thread overview]
Message-ID: <CAAuqQpRd8Pv==ijz5yHV6a3HX=XO_tkU60QHWqKdGZ6d5VBENQ@mail.gmail.com> (raw)
In-Reply-To: <CAAuqQpRd6=g7hA5knDH3yCD9Bmdtqfi8fJ4CjdR3JeroQfQCNg@mail.gmail.com>

Hi Lijuan,

The DTS started without error but the nic single core test failed on a
"connection timeout - no response from TRex server" when I tried to run it
on an intel nic.
This happens when DTS uses arm-dell (traffic generator) to send packets
to arm-gigabyte (DUT) using the Intel nic {Ethernet Controller XL710 for
40GbE QSFP+}
I wonder if you have any clue on this issue?

19/11/2020 19:05:55          TestNicSingleCorePerf: Test Case
test_perf_nic_single_core Result ERROR: Traceback (most recent call last):
  File "/opt/dts/framework/test_case.py", line 319, in _execute_test_case
    case_obj()
  File "tests/TestSuite_nic_single_core_perf.py", line 200, in
test_perf_nic_single_core
    self.perf_test(self.nb_ports)
  File "tests/TestSuite_nic_single_core_perf.py", line 274, in perf_test
    _, packets_received =
self.tester.pktgen.measure_throughput(stream_ids=streams,
options=traffic_opt)
  File "/opt/dts/framework/pktgen_base.py", line 245, in measure_throughput
    self._prepare_transmission(stream_ids=stream_ids)
  File "/opt/dts/framework/pktgen_trex.py", line 778, in
_prepare_transmission
    self._conn.reset(ports=self._ports)
  File
"/opt/trex-v2.85/automation/trex_control_plane/interactive/trex/common/trex_api_annotators.py",
line 51, in wrap2
    ret = f(*args, **kwargs)
  File
"/opt/trex-v2.85/automation/trex_control_plane/interactive/trex/stl/trex_stl_client.py",
line 339, in reset
    self.clear_stats(ports)
  File
"/opt/trex-v2.85/automation/trex_control_plane/interactive/trex/common/trex_api_annotators.py",
line 51, in wrap2
    ret = f(*args, **kwargs)
  File
"/opt/trex-v2.85/automation/trex_control_plane/interactive/trex/stl/trex_stl_client.py",
line 1492, in clear_stats
    self._clear_stats_common(ports, clear_global, clear_xstats)
  File
"/opt/trex-v2.85/automation/trex_control_plane/interactive/trex/common/trex_client.py",
line 2876, in _clear_stats_common
    raise TRexError(rc)
trex.common.trex_exceptions.TRexError: ^[[1m*** [RPC] - Failed to get
server response from tcp://172.18.0.40:4501^[[22m

19/11/2020 19:05:55                            dts:
TEST SUITE ENDED: TestNicSingleCorePerf
19/11/2020 19:06:11          TestNicSingleCorePerf: tear_down_all failed:
Traceback (most recent call last):
  File "/opt/dts/framework/test_case.py", line 430, in execute_tear_downall
    self.tear_down_all()
  File "tests/TestSuite_nic_single_core_perf.py", line 405, in tear_down_all
    self.dut.build_install_dpdk(self.target)
  File "/opt/dts/framework/project_dpdk.py", line 283, in build_install_dpdk
    build_install_dpdk(target, extra_options)
  File "/opt/dts/framework/project_dpdk.py", line 316, in
build_install_dpdk_linux_meson
    self.send_expect("rm -rf " + target, "#")
  File "/opt/dts/framework/crb.py", line 93, in send_expect
    return self.session.send_expect(cmds, expected, timeout, verify)
  File "/opt/dts/framework/ssh_connection.py", line 64, in send_expect
    out = self.session.send_expect(cmds, expected, timeout, verify)
  File "/opt/dts/framework/ssh_pexpect.py", line 103, in send_expect
    raise(e)
  File "/opt/dts/framework/ssh_pexpect.py", line 90, in send_expect
    ret = self.send_expect_base(command, expected, timeout)
  File "/opt/dts/framework/ssh_pexpect.py", line 81, in send_expect_base
    self.__prompt(command, timeout)
  File "/opt/dts/framework/ssh_pexpect.py", line 149, in __prompt
    raise TimeoutException(command, self.get_output_all()) from None
exception.TimeoutException: TIMEOUT on rm -rf x86_64-native-linuxapp-gcc

Thanks,
David

On Thu, Nov 19, 2020 at 12:56 PM David Liu <dliu@iol.unh.edu> wrote:

> Hi Lijuan,
>
> Thank you for the help.
> I can run DTS without that error now,
>
> Thanks,
> David
>
> On Tue, Nov 17, 2020 at 9:12 PM Tu, Lijuan <lijuan.tu@intel.com> wrote:
>
>> Hi David,
>>
>>
>>
>> Snice some protocols are only supported by scapy 2.4.4, it's recemented
>> that scapy 2.4.4 as major version for DTS.
>>
>> However perf users might not care these advanced protocols, to be
>> compatible with trex, dts captured these exceptions and let it go through.
>>
>> Fix was contained in the latest DTS. Could you update it.
>>
>>
>>
>> commit 362ae41844e1992163b4eed53a721729985644be
>>
>> Author: Chen, BoX C <box.c.chen@intel.com>
>>
>> Date:   Wed Nov 4 10:52:09 2020 +0800
>>
>>
>>
>>     framework: fix Trex mode not working
>>
>>     DTS requires Trex compatible scapy, modify package loading mode and
>> scapy version verification rules
>>
>>
>>
>>     Signed-off-by: Chen, BoX C <box.c.chen@intel.com>
>>
>>
>>
>>
>>
>> *From:* David Liu <dliu@iol.unh.edu>
>> *Sent:* 2020年11月18日 4:24
>> *To:* Tu, Lijuan <lijuan.tu@intel.com>
>> *Cc:* dpdk-dev <dev@dpdk.org>
>> *Subject:* DTS Test Nic Single Core Perf Scapy Naming Conflict
>>
>>
>>
>> Hi Lijuan,
>>
>>
>>
>> I currently have issues with running the Nic Single-Core Perf Test.
>>
>> I believe this is the scapy naming conflict issue, so I follow the
>> solution
>>
>> mentioned on the website to replace system scapy with trex scapy.
>>
>> Then I got into another error that I wasn't able to get pass:
>>
>>
>>
>> root@arm-dell:/opt/dts# ./dts
>> Traceback (most recent call last):
>>   File "./main.py", line 50, in <module>
>>     import dts
>>   File "/opt/dts/framework/dts.py", line 47, in <module>
>>     from tester import Tester
>>   File "/opt/dts/framework/tester.py", line 52, in <module>
>>     from packet import SCAPY_IMP_CMD
>>   File "/opt/dts/framework/packet.py", line 72, in <module>
>>     locals().update({clazz: getattr(module, clazz)})
>> AttributeError: module 'scapy.contrib.gtp' has no attribute
>> 'GTPPDUSessionContainer'
>>
>>
>>
>> Do you have any clue how to fix this?
>>
>>
>>
>> Thanks.
>>
>> David
>>
>

  reply	other threads:[~2020-11-19 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 20:23 David Liu
2020-11-18  2:12 ` Tu, Lijuan
2020-11-19 17:56   ` David Liu
2020-11-19 19:34     ` David Liu [this message]
2020-11-20  2:10       ` Tu, Lijuan
2020-11-24 20:08         ` David Liu
2020-11-27  1:07           ` Tu, Lijuan

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='CAAuqQpRd8Pv==ijz5yHV6a3HX=XO_tkU60QHWqKdGZ6d5VBENQ@mail.gmail.com' \
    --to=dliu@iol.unh.edu \
    --cc=dev@dpdk.org \
    --cc=lijuan.tu@intel.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).