From: Yinan Wang <yinan.wang@intel.com>
To: dts@dpdk.org
Cc: Yinan Wang <yinan.wang@intel.com>
Subject: [dts] [PATCH v1] test_plans/packet_capture_test_plan.rst
Date: Thu, 20 Aug 2020 06:00:34 -0400 [thread overview]
Message-ID: <20200820100034.15541-1-yinan.wang@intel.com> (raw)
Add test prerequisites in test plan
Signed-off-by: Yinan Wang <yinan.wang@intel.com>
---
test_plans/packet_capture_test_plan.rst | 20 +++++++++++++++++---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/test_plans/packet_capture_test_plan.rst b/test_plans/packet_capture_test_plan.rst
index 05629d0..2f38b60 100644
--- a/test_plans/packet_capture_test_plan.rst
+++ b/test_plans/packet_capture_test_plan.rst
@@ -59,8 +59,8 @@ DPDK technical doc refer to::
dpdk/doc/guides/tools/pdump.rst
-Prerequisites
-=============
+Test configuration
+==================
2x NICs (2 full duplex ports per NIC) plugged into the available slots on a
platform, another two nic ports are linked with cables.
@@ -83,6 +83,20 @@ note: portB0/portB1 are the binded ports.
portB2/portB3 keep link up status and don't bind to dpdk driver.
Except portB0/portB1, DUT should have other two ports on link up status
+Prerequisites
+=============
+
+Enable pcap lib in dpdk code and recompile::
+
+ --- a/config/common_base
+ +++ b/config/common_base
+ @@ -492,7 +492,7 @@ CONFIG_RTE_LIBRTE_PMD_NULL=y
+ #
+ # Compile software PMD backed by PCAP files
+ #
+ -CONFIG_RTE_LIBRTE_PMD_PCAP=n
+ +CONFIG_RTE_LIBRTE_PMD_PCAP=y
+
Test cases
==========
@@ -539,4 +553,4 @@ steps:
pkt=rdpcap('xxxx1.pcap')
pkt[0].show2()
pkt=rdpcap('xxxx2.pcap')
- pkt[0].show2()
\ No newline at end of file
+ pkt[0].show2()
--
2.17.1
next reply other threads:[~2020-08-20 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 10:00 Yinan Wang [this message]
2020-08-27 1:59 ` 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=20200820100034.15541-1-yinan.wang@intel.com \
--to=yinan.wang@intel.com \
--cc=dts@dpdk.org \
/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).