From: Ferruh Yigit <ferruh.yigit@intel.com>
To: ogawa.yasufumi@lab.ntt.co.jp, spp@dpdk.org
Subject: Re: [spp] [PATCH 0/6] Improve use of pcap PMD
Date: Mon, 28 May 2018 13:29:55 +0100 [thread overview]
Message-ID: <6623615b-753e-ba33-73fd-69fbf96209bd@intel.com> (raw)
In-Reply-To: <20180515012146.8899-1-ogawa.yasufumi@lab.ntt.co.jp>
On 5/15/2018 2:21 AM, ogawa.yasufumi@lab.ntt.co.jp wrote:
> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>
> Hi,
>
> To use pcap PMD, user should prepare rx_pcap before launching SPP,
> or failed to not found. This update is for creating rx_pcap device
> before adding pcap PMD to avoid the error.
>
> It is required to install text2pap, which is included in wireshark,
> to create pcap file.
>
> This update is also including requirements for text2pcap and usecases
> for describing the usage of pcap PMD.
>
> Thanks,
> Yasufumi
>
>
> Yasufumi Ogawa (6):
> docs: add setting up PCAP
> spp_nfv: update for creating rx pcap device
> docs: add installing text2pcap for pcap PMD
> docs: add usecase of pcap PMD
> docs: add images of usecase of pcap PMD
> docs: add references for images for pcap PMD
Series applied, thanks.
prev parent reply other threads:[~2018-05-28 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 1:21 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 ` [spp] [PATCH 6/6] docs: add references for images for " ogawa.yasufumi
2018-05-28 12:29 ` Ferruh Yigit [this message]
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=6623615b-753e-ba33-73fd-69fbf96209bd@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--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).