From: David Liu <dliu@iol.unh.edu>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: ci@dpdk.org, dpdklab <dpdklab@iol.unh.edu>
Subject: Re: [dpdk-ci] [DPDKLAB] 25G Broadcom NIC in Arm hardware
Date: Tue, 2 Feb 2021 11:58:03 -0500 [thread overview]
Message-ID: <CAAuqQpRK9J45HL8uqbSvpP0m0XiZRxWL6CPFprbiivhkZSN_hw@mail.gmail.com> (raw)
In-Reply-To: <CAAuqQpTT-ck1vPQuDKv2jhD_tCqZC-urL4-XgutkSxqpwyPznw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 9383 bytes --]
Hi Ajit,
Ping again in case if you miss the last email.
Did you have a chance to give it a try on login to the machines?
Just some notes, we are currently running compile and some
performance/functional testing.
Which it may be hard for you to run dts, so please let me know if you want
me to stop these tests for you to debug.
Step I run:
CONF="conf_dpdk" ./switch.sh Broadcom #this is to switch the
dts configuration to Broadcom
./dts -s #To
start the dts
Informatio:
arm-dell.dpdklab.iol.unh.edu
- dts - located in /opt/dts
- Trex - located in /opt/trex/v2.87
arm-gigabyte.dpdklab.iol.unh.edu
- dpdk - located in /root/dpdk
Best,
David
On Tue, Jan 26, 2021 at 4:59 PM David Liu <dliu@iol.unh.edu> wrote:
> Also, I had changed the configuration when I run Broadcom nic.
> In the dts folder, you can start it with ./dts -s
>
> On Tue, Jan 26, 2021 at 4:54 PM David Liu <dliu@iol.unh.edu> wrote:
>
>> Hi Ajit,
>> Sorry for the late reply.
>>
>> You can ssh into the machine using the same VPN Username and Password.
>> Can you try and see if that works?
>>
>> Informatio:
>> arm-dell.dpdklab.iol.unh.edu
>> - dts - located in /opt/dts
>> - Trex - located in /opt/trex/v2.87
>>
>> arm-gigabyte.dpdklab.iol.unh.edu
>> - dpdk - located in /root/dpdk
>>
>>
>> Thanks,
>> David
>>
>> On Tue, Jan 19, 2021 at 5:20 PM Ajit Khaparde <ajit.khaparde@broadcom.com>
>> wrote:
>>
>>> Hi David,
>>> Thanks for pinging me. Do you think I could login into the setup and
>>> see what is happening?
>>> I do have the credentials for two systems in your lab -
>>> rhea.dpdklab.iol.unh.edu and io.dpdklab.iol.unh.edu
>>> If you can provide me details of the systems you are trying to
>>> configure, I could take a look.
>>>
>>> Thanks
>>> Ajit
>>>
>>> On Tue, Jan 19, 2021 at 1:41 PM David Liu <dliu@iol.unh.edu> wrote:
>>> >
>>> > Hi Ajit,
>>> >
>>> > Thank you for helping out.
>>> >
>>> > How are you doing with this issue?
>>> >
>>> > Please let me know if you need anything information from us.
>>> >
>>> > Just some extra information that both Trex and dts are on the same
>>> intel tester machine.
>>> >
>>> > Best,
>>> > David
>>> >
>>> > On Thu, Jan 14, 2021 at 2:12 PM David Liu <dliu@iol.unh.edu> wrote:
>>> >>
>>> >> Yes, so this is the same NIC work on x86.
>>> >> By seeing the link, I am assuming you mean the ports that are using
>>> for Trex. If so they are UP before I start the Trex.
>>> >>
>>> >> Thank,
>>> >> David
>>> >>
>>> >>
>>> >> On Thu, Jan 14, 2021 at 1:11 AM Ajit Khaparde <
>>> ajit.khaparde@broadcom.com> wrote:
>>> >>>
>>> >>> Does the same NIC work on x86?
>>> >>> Also do you see link before you start the trex? I am trying to see
>>> if the port failed to successfully come up
>>> >>> or if there is a problem with the link. Can you check and tell?
>>> >>>
>>> >>> Thanks
>>> >>> Ajit
>>> >>>
>>> >>> On Wed, Jan 13, 2021 at 4:20 PM David Liu <dliu@iol.unh.edu> wrote:
>>> >>>>
>>> >>>> Hi Ajit,
>>> >>>>
>>> >>>> Thank you for helping out.
>>> >>>>
>>> >>>> We have it working on the x86, but not the Arm.
>>> >>>>
>>> >>>>
>>> >>>> Thanks,
>>> >>>> David
>>> >>>>
>>> >>>> On Wed, Jan 13, 2021 at 5:34 PM Ajit Khaparde <
>>> ajit.khaparde@broadcom.com> wrote:
>>> >>>>>
>>> >>>>> Hi David,
>>> >>>>> I will take a look.
>>> >>>>> Do you see similar issues on x86? I am asking because
>>> >>>>> even I would start with that to create a baseline and then
>>> >>>>> attempt on ARM.
>>> >>>>>
>>> >>>>> Thanks
>>> >>>>> Ajit
>>> >>>>>
>>> >>>>> On Wed, Jan 13, 2021 at 12:08 PM David Liu <dliu@iol.unh.edu>
>>> wrote:
>>> >>>>>>
>>> >>>>>> Hi Ajit,
>>> >>>>>>
>>> >>>>>> We have a 25G Broadcom NIC that is installed on an Arm machine.
>>> >>>>>> And I am running into a problem when I try to run
>>> nic_single_core_perf on the NIC.
>>> >>>>>> Currently, we are using: Trex v2.86 and dts from
>>> http://git.dpdk.org/tools/dts/
>>> >>>>>> All the NICs are up and running when testing.
>>> >>>>>>
>>> >>>>>> The problem is an error when I try to run the test case inside
>>> the nic_single_core_perf:
>>> >>>>>>
>>> >>>>>>> TestNicSingleCorePerf: Test running at parameters: framesize:
>>> 64, rxd/txd: 512
>>> >>>>>>> dut.172.18.0.41:
>>> x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 32,33 -n 4
>>> --file-prefix=dpdk_15311_20210113190237 -a 0000:93:00.0 -a 0000:93:00.1
>>> -- -i --portmask=0x3 --txd=512 --rxd=512 --nb-cores=1
>>> >>>>>>> dut.172.18.0.41: start
>>> >>>>>>> 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 196, in
>>> test_perf_nic_single_core
>>> >>>>>>> self.perf_test(self.nb_ports)
>>> >>>>>>> File "tests/TestSuite_nic_single_core_perf.py", line 270, 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.86/automation/trex_control_plane/interactive/trex/common/trex_api_annotators.py",
>>> line 51, in wrap2
>>> >>>>>>> ret = f(*args, **kwargs)
>>> >>>>>>> File
>>> "/opt/trex/v2.86/automation/trex_control_plane/interactive/trex/stl/trex_stl_client.py",
>>> line 339, in reset
>>> >>>>>>> self.clear_stats(ports)
>>> >>>>>>> File
>>> "/opt/trex/v2.86/automation/trex_control_plane/interactive/trex/common/trex_api_annotators.py",
>>> line 51, in wrap2
>>> >>>>>>> ret = f(*args, **kwargs)
>>> >>>>>>> File
>>> "/opt/trex/v2.86/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.86/automation/trex_control_plane/interactive/trex/common/trex_client.py",
>>> line 2876, in _clear_stats_common
>>> >>>>>>> raise TRexError(rc)
>>> >>>>>>> trex.common.trex_exceptions.TRexError: *** [RPC] - Failed to get
>>> server response from tcp://172.18.0.40:4501
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> I also try to run TRex in stateless mode with./t-rex-64 -i --cfg
>>> /etc/trex_cfg.yaml and connect with ./trex-console
>>> >>>>>>
>>> >>>>>> Then start sending traffic with command
>>> >>>>>>>
>>> >>>>>>> trex>start -f stl/imix.py
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> But this will cause an error to turn off Trex.
>>> >>>>>>
>>> >>>>>>> trex>
>>> >>>>>>> 2021-01-13 19:56:21 - [server][warning] - Server has been
>>> shutdown - cause: 'WATCHDOG: task 'Trex DP core 1' has not responded for
>>> more than 1.00135 seconds - timeout is 1 seconds
>>> >>>>>>> *** traceback follows ***
>>> >>>>>>> 1 0x561be173cf5a ./_t-rex-64(+0x19af5a) [0x561be173cf5a]
>>> >>>>>>> 2 0x7feea3ac0980
>>> /lib/x86_64-linux-gnu/libpthread.so.0(+0x12980) [0x7feea3ac0980]
>>> >>>>>>> 3 0x561be1a05a2a rte_delay_us_block + 106
>>> >>>>>>> 4 0x561be16ce874 CCoreEthIF::send_burst(CCorePerPort*,
>>> unsigned short, CVirtualIFPerSideStats*) + 3220
>>> >>>>>>> 5 0x561be16abf57 CCoreEthIF::flush_tx_queue() + 31
>>> >>>>>>> 6 0x561be171e3d9
>>> CNodeGenerator::handle_maintenance(CFlowGenListPerThread*) + 265
>>> >>>>>>> 7 0x561be171f7ec
>>> CNodeGenerator::handle_flow_sync(CGenNode*, CFlowGenListPerThread*, bool&)
>>> + 92
>>> >>>>>>> 8 0x561be171fc98
>>> CNodeGenerator::handle_slow_messages(unsigned char, CGenNode*,
>>> CFlowGenListPerThread*, bool) + 184
>>> >>>>>>> 9 0x561be16cb5f1 int
>>> CNodeGenerator::flush_file_realtime<23, false>(double, double,
>>> CFlowGenListPerThread*, double&) + 881
>>> >>>>>>> 10 0x561be1905212 TrexStatelessDpCore::start_scheduler() +
>>> 226
>>> >>>>>>> 11 0x561be1883ae9 TrexDpCore::start() + 89
>>> >>>>>>> 12 0x561be1714113
>>> CFlowGenListPerThread::start(std::__cxx11::basic_string<char,
>>> std::char_traits<char>, std::allocator<char> >&, CPreviewMode&) + 115
>>> >>>>>>> 13 0x561be16af8dd CGlobalTRex::run_in_core(unsigned char) +
>>> 487
>>> >>>>>>> 14 0x561be16d11ad ./_t-rex-64(+0x12f1ad) [0x561be16d11ad]
>>> >>>>>>> 15 0x561be1a1dfaa eal_thread_loop + 426
>>> >>>>>>> 16 0x7feea3ab56db
>>> /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7feea3ab56db]
>>> >>>>>>> 17 0x7feea2a8571f clone + 63
>>> >>>>>>>
>>> >>>>>>> *** addr2line information follows ***
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> ??:0
>>> >>>>>>> '
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> I believe if everything is working, this should not turn off trex
>>> but please correct me if I am wrong.
>>> >>>>>> I wonder if you have any suggestion of how I can approach this
>>> issue?
>>> >>>>>>
>>> >>>>>> Best,
>>> >>>>>> David
>>> >>>>>>
>>> >>>>>>
>>>
>>
[-- Attachment #2: Type: text/html, Size: 14334 bytes --]
next prev parent reply other threads:[~2021-02-02 16:58 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 20:07 David Liu
2021-01-13 22:34 ` Ajit Khaparde
2021-01-14 0:19 ` David Liu
2021-01-14 6:11 ` Ajit Khaparde
2021-01-14 19:12 ` David Liu
2021-01-19 21:40 ` David Liu
2021-01-19 22:19 ` Ajit Khaparde
2021-01-26 21:54 ` David Liu
2021-01-26 21:59 ` David Liu
2021-02-02 16:58 ` David Liu [this message]
2021-02-02 18:57 ` Ajit Khaparde
2021-02-08 4:03 ` Ajit Khaparde
2021-02-09 14:35 ` David Liu
2021-02-12 2:38 ` Ajit Khaparde
[not found] ` <CAHx6DYDLOBOMMo_vfB0YAhLcQMbDV3-H=RY6Oa+Tp7tWdFxo8A@mail.gmail.com>
2021-02-12 22:48 ` [dpdk-ci] [dpdklab] " Ajit Khaparde
2021-02-18 18:00 ` David Liu
2021-02-18 18:03 ` Ajit Khaparde
2021-02-23 4:10 ` Ajit Khaparde
2021-02-25 17:55 ` David Liu
2021-02-25 18:46 ` David Liu
2021-03-01 15:00 ` Juraj Linkeš
2021-03-01 15:12 ` Ajit Khaparde
2021-03-02 14:28 ` David Liu
2021-03-02 15:27 ` Ajit Khaparde
2021-03-02 18:05 ` David Liu
2021-03-03 9:05 ` Juraj Linkeš
2021-03-05 21:29 ` David Liu
2021-03-05 22:06 ` Ajit Khaparde
2021-03-08 1:07 ` Ajit Khaparde
2021-03-09 14:23 ` David Liu
2021-03-09 16:56 ` Ajit Khaparde
2021-03-09 19:00 ` Ajit Khaparde
2021-03-11 14:01 ` David Liu
2021-03-11 17:05 ` Ajit Khaparde
2021-03-16 15:31 ` David Liu
2021-03-16 15:43 ` Ajit Khaparde
2021-04-01 17:09 ` David Liu
2021-04-05 14:25 ` Ajit Khaparde
2021-04-06 14:29 ` David Liu
2021-04-07 20:16 ` Ajit Khaparde
2021-04-09 22:09 ` David Liu
2021-04-09 23:34 ` Ajit Khaparde
2021-04-15 17:07 ` David Liu
2021-04-21 7:39 ` Juraj Linkeš
2021-04-21 14:20 ` Ajit Khaparde
2021-04-22 3:55 ` David Liu
2021-04-22 6:50 ` Juraj Linkeš
2021-04-27 14:09 ` David Liu
2021-04-28 1:19 ` Ajit Khaparde
2021-04-28 6:48 ` Ajit Khaparde
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=CAAuqQpRK9J45HL8uqbSvpP0m0XiZRxWL6CPFprbiivhkZSN_hw@mail.gmail.com \
--to=dliu@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).