From: Brandon Lo <blo@iol.unh.edu>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: ci@dpdk.org, dpdklab <dpdklab@iol.unh.edu>
Subject: Re: [dpdk-ci] New 100G Broadcom NIC Ubuntu
Date: Tue, 4 Aug 2020 12:16:09 -0400 [thread overview]
Message-ID: <CAOeXdvZWEitiCws3ALwwxN7dP0rfjWBs9AnpsZ=aF9i3W0Afig@mail.gmail.com> (raw)
In-Reply-To: <CAOeXdvYQ-Krd2FKo_gQkAP32+KyQAoM+DFRy4OftyiocTJKhNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2568 bytes --]
Hi Ajit,
I'm running into a problem with trying to run nic_single_core_perf on the
new NIC.
The current configuration uses trex version v2.82.
However, I'm running into an error when it tries to actually do a test case
in the nic_single_core_perf.
The output looks like this when it reaches a test case:
TestNicSingleCorePerf: Test running at parameters: framesize: 64, rxd/txd:
> 512
> dut.rhea: ./x86_64-native-linuxapp-gcc/app/testpmd
> -l 16,17 -n 4 -w 0000:81:00.0 -w 0000:81:00.1
> --file-prefix=dpdk_11307_20200804160513 -- -i --portmask=0x3 --txd=512
> --rxd=512
> dut.rhea: start
> TestNicSingleCorePerf: Test Case test_perf_nic_single_core Result
> ERROR: Traceback (most recent call last):
> File "/opt/dts/framework/test_case.py", line 316, in _execute_test_case
> case_obj()
> File "tests/TestSuite_nic_single_core_perf.py", line 198, in
> test_perf_nic_single_core
> self.perf_test(self.nb_ports)
> File "tests/TestSuite_nic_single_core_perf.py", line 259, 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 779, in
> _prepare_transmission
> self._conn.reset(ports=self._ports)
> File
> "/opt/v2.82/automation/trex_control_plane/interactive/trex/common/trex_api_annotators.py",
> line 51, in wrap2
> ret = f(*args, **kwargs)
> File
> "/opt/v2.82/automation/trex_control_plane/interactive/trex/stl/trex_stl_client.py",
> line 339, in reset
> self.clear_stats(ports)
> File
> "/opt/v2.82/automation/trex_control_plane/interactive/trex/common/trex_api_annotators.py",
> line 51, in wrap2
> ret = f(*args, **kwargs)
> File
> "/opt/v2.82/automation/trex_control_plane/interactive/trex/stl/trex_stl_client.py",
> line 1467, in clear_stats
> self._clear_stats_common(ports, clear_global, clear_xstats)
> File
> "/opt/v2.82/automation/trex_control_plane/interactive/trex/common/trex_client.py",
> line 2840, in _clear_stats_common
> raise TRexError(rc)
> trex.common.trex_exceptions.TRexError: *** [RPC] - Failed to get server
> response from tcp://127.0.0.1:4501
I have found one similar case on the github repository for trex, but the
solution was vendor-specific:
https://github.com/cisco-system-traffic-generator/trex-core/issues/147.
Have you ran into this issue before?
Thanks,
Brandon
[-- Attachment #2: Type: text/html, Size: 3598 bytes --]
next prev parent reply other threads:[~2020-08-04 16:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 20:22 Brandon Lo
2020-07-21 21:27 ` Ajit Khaparde
2020-07-28 16:47 ` Brandon Lo
2020-07-28 17:22 ` Ajit Khaparde
2020-07-28 17:32 ` Brandon Lo
2020-07-28 19:19 ` Ajit Khaparde
2020-07-28 19:41 ` Brandon Lo
2020-08-04 16:16 ` Brandon Lo [this message]
2020-08-04 16:37 ` Ajit Khaparde
2020-08-04 17:42 ` Brandon Lo
2020-08-11 17:45 ` Brandon Lo
2020-08-11 17:47 ` Ajit Khaparde
2020-08-20 4:29 ` Ajit Khaparde
2020-08-20 15:39 ` Brandon Lo
2020-08-20 21:07 ` Ajit Khaparde
2020-08-25 20:13 ` Brandon Lo
2020-08-26 19:57 ` Ajit Khaparde
2020-09-01 18:09 ` Brandon Lo
2020-09-01 18:11 ` Ajit Khaparde
2020-10-22 19:03 ` Brandon Lo
2020-10-22 19:27 ` Ajit Khaparde
2020-12-03 16:48 ` [dpdk-ci] [dpdklab] " Brandon Lo
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='CAOeXdvZWEitiCws3ALwwxN7dP0rfjWBs9AnpsZ=aF9i3W0Afig@mail.gmail.com' \
--to=blo@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--cc=ci@dpdk.org \
--cc=dpdklab@iol.unh.edu \
/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).