From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org
Cc: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Subject: [spp] [PATCH 6/6] docs: add references for images for pcap PMD
Date: Tue, 15 May 2018 10:21:46 +0900 [thread overview]
Message-ID: <20180515012146.8899-7-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <20180515012146.8899-1-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/setup/use_cases.rst | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/docs/guides/setup/use_cases.rst b/docs/guides/setup/use_cases.rst
index 06f4b45..1cd30a6 100644
--- a/docs/guides/setup/use_cases.rst
+++ b/docs/guides/setup/use_cases.rst
@@ -414,6 +414,14 @@ As the first usecase, add a pcap PMD and capture incoming packets from
spp > sec 1;patch phy:0 pcap:1
spp > sec 1;forward
+.. _figure_spp_pcap_incoming:
+
+.. figure:: ../images/setup/use_cases/spp_pcap_incoming.*
+ :height: 380 em
+ :width: 380 em
+
+ Rapture incoming packets
+
In this example, we use pktgen.
Once you start forwarding packets from pktgen, you can see
that the size of ``/tmp/spp-tx1.pcap`` is increased rapidly
@@ -448,6 +456,14 @@ Then, add pcap PMD to another ``spp_nfv`` with index ``2``.
spp > sec 2;add pcap 2
+.. _figure_spp_pcap_restoring:
+
+.. figure:: ../images/setup/use_cases/spp_pcap_restoring.*
+ :height: 380 em
+ :width: 380 em
+
+ Restore dumped packets
+
You can find that ``spp-tx2.pcap`` is creaeted and ``spp-rx2.pcap``
still remained.
--
2.17.0
next prev parent reply other threads:[~2018-05-15 1:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 1:21 [spp] [PATCH 0/6] Improve use of " ogawa.yasufumi
2018-05-15 1:21 ` [spp] [PATCH 1/6] docs: add setting up PCAP ogawa.yasufumi
2018-05-15 1:21 ` [spp] [PATCH 2/6] spp_nfv: update for creating rx pcap device ogawa.yasufumi
2018-05-15 1:21 ` [spp] [PATCH 3/6] docs: add installing text2pcap for pcap PMD ogawa.yasufumi
2018-05-15 1:21 ` [spp] [PATCH 4/6] docs: add usecase of " ogawa.yasufumi
2018-05-15 1:21 ` [spp] [PATCH 5/6] docs: add images of " ogawa.yasufumi
2018-05-15 1:21 ` ogawa.yasufumi [this message]
2018-05-28 12:29 ` [spp] [PATCH 0/6] Improve use " Ferruh Yigit
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=20180515012146.8899-7-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@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).