From: x-fn-spp@sl.ntt-tx.co.jp
To: ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Cc: spp@dpdk.org
Subject: [spp] [PATCH v2 0/7] introduce new feature SPP PCAP
Date: Fri, 8 Feb 2019 17:44:31 +0900 [thread overview]
Message-ID: <201902080844.x188icZn030802@imss04.silk.ntt-tx.co.jp> (raw)
From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
V2:
1.Update source fixing bug not freeing mbuf correctly.
V1:
This patch series provides new feature called SPP PCAP.
spp_pcap is a new secondary process for capturing incoming packets.
This secondary process is intended to cover operator and/or developer
needs to capture packets. For such use, spp_pcap provides packet
capturing feature from specific port. It is aimed to capture up to
10Gbps packets.
Hideyuki Yamashita (7):
spp_pcap: add command main
spp_pcap: add command decode
spp_pcap: add management function
spp_pcap: add spp_pcap main function
spp_pcap: add Makefile for spp_pcap
controller: add SppPcap class
controller: add pcap command to SPP controller
src/Makefile | 1 +
src/controller/commands/pcap.py | 230 +++++++
src/controller/shell.py | 87 ++-
src/pcap/Makefile | 36 +
src/pcap/command_dec.c | 187 ++++++
src/pcap/command_dec.h | 110 ++++
src/pcap/command_proc.c | 976 +++++++++++++++++++++++++++
src/pcap/command_proc.h | 42 ++
src/pcap/spp_pcap.c | 1091 +++++++++++++++++++++++++++++++
src/pcap/spp_pcap.h | 35 +
src/pcap/spp_proc.c | 289 ++++++++
src/pcap/spp_proc.h | 389 +++++++++++
12 files changed, 3470 insertions(+), 3 deletions(-)
create mode 100644 src/controller/commands/pcap.py
create mode 100644 src/pcap/Makefile
create mode 100644 src/pcap/command_dec.c
create mode 100644 src/pcap/command_dec.h
create mode 100644 src/pcap/command_proc.c
create mode 100644 src/pcap/command_proc.h
create mode 100644 src/pcap/spp_pcap.c
create mode 100644 src/pcap/spp_pcap.h
create mode 100644 src/pcap/spp_proc.c
create mode 100644 src/pcap/spp_proc.h
--
2.17.1
reply other threads:[~2019-02-08 8:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201902080844.x188icZn030802@imss04.silk.ntt-tx.co.jp \
--to=x-fn-spp@sl.ntt-tx.co.jp \
--cc=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).