From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: David Liu <dliu@iol.unh.edu>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] DTS Test Nic Single Core Perf Scapy Naming Conflict
Date: Wed, 18 Nov 2020 02:12:02 +0000 [thread overview]
Message-ID: <e4cb5c04c97940d29d0a392f55c71d62@intel.com> (raw)
In-Reply-To: <CAAuqQpQ7h2bE7-S_LT557E_OjNi2ZXvgDOE6pRX7FLY49QCPkw@mail.gmail.com>
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
next prev parent reply other threads:[~2020-11-18 2:12 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 [this message]
2020-11-19 17:56 ` David Liu
2020-11-19 19:34 ` David Liu
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=e4cb5c04c97940d29d0a392f55c71d62@intel.com \
--to=lijuan.tu@intel.com \
--cc=dev@dpdk.org \
--cc=dliu@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).