Re: [dpdk-dev] DTS Config NIC | Test Nic Single Core Perf ISSUE

["Tu, Lijuan" <lijuan.tu@intel.com>]

That’s because scapy naming conflict, replace system scapy with trex scapy.


Here is an example:



# backup system scapy if need.

mv  /usr/local/lib/python3.6/dist-packages/scapy /usr/local/lib/python3.6/dist-packages/scapy_default

# replace scapy

cp -fr /home/scm/trex1911_upstream/scripts/external_libs/scapy-2.3.1/python3/scapy /usr/local/lib/python3.6/dist-packages/scapy



vim /usr/local/lib/python3.6/dist-packages/scapy/utils.py

line 820:

        #import scapy.plist

        #return scapy.plist.PacketList(res,name = os.path.basename(self.filename))

        from scapy import plist

        return plist.PacketList(res,name = os.path.basename(self.filename))


From: David Liu [mailto:dliu@iol.unh.edu]
Sent: Friday, April 3, 2020 3:53 AM
To: Tu, Lijuan <lijuan.tu@intel.com>
Cc: dev@dpdk.org
Subject: DTS Config NIC | Test Nic Single Core Perf ISSUE

Hi Lijuan,

We are currently having issues with the Test Nic Single Core Perf Test.
First we have issues with fortville_eagle was not in the set_up_all in the TestSuite_nic_single_core_perf.py.
So we added  fortville_eagle': {64: {512: 0.00, 2048: 0.00}} to the Test Nic Single Core Perf configuration file.
But now it is causing other issues, do you have any clue how we can fix this?

Thanks,
David