From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: spp@dpdk.org
Cc: ferruh.yigit@intel.com, x-fn-spp@sl.ntt-tx.co.jp
Subject: Re: [spp] [PATCH v3 0/9] Introduce spp_pcap
Date: Wed, 13 Feb 2019 14:55:47 +0900 [thread overview]
Message-ID: <b344b68d-75cb-4f02-1f21-e28c87cd904e@lab.ntt.co.jp> (raw)
In-Reply-To: <1549768101-23049-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>
> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>
> Hideyuki,
>
> Thank you for your contribution. Some of patches are still needed to be
> revised. This series of patches is a revised version.
>
> * Correct initialization of SppPcap and fix `exit` command does not
> work.
>
> * Correct wrong comments shown in help.
>
> * Revise commit messages and miscs in codes.
>
> Yasufumi
>
> Hideyuki Yamashita (7):
> spp_pcap: add command main
> spp_pcap: add command parser functions
> spp_pcap: add management data and utilities
> spp_pcap: add main and related functions
> spp_pcap: update Makefile
> controller: add SppPcap class
> controller: add pcap command to SPP controller
>
> Yasufumi Ogawa (2):
> controlle: refactor pcap command
> controller: fix init of pcap instances
Series of patches applied. Thanks.
>
> src/Makefile | 1 +
> src/controller/commands/pcap.py | 226 ++++++++
> src/controller/shell.py | 80 ++-
> 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, 3459 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
>
--
Yasufumi Ogawa
NTT Network Service Systems Labs
prev parent reply other threads:[~2019-02-13 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 3:08 ogawa.yasufumi
2019-02-10 3:08 ` [spp] [PATCH v3 1/9] spp_pcap: add command main ogawa.yasufumi
2019-02-10 3:08 ` [spp] [PATCH v3 2/9] spp_pcap: add command parser functions ogawa.yasufumi
2019-02-10 3:08 ` [spp] [PATCH v3 3/9] spp_pcap: add management data and utilities ogawa.yasufumi
2019-02-10 3:08 ` [spp] [PATCH v3 4/9] spp_pcap: add main and related functions ogawa.yasufumi
2019-02-10 3:08 ` [spp] [PATCH v3 5/9] spp_pcap: update Makefile ogawa.yasufumi
2019-02-10 3:08 ` [spp] [PATCH v3 6/9] controller: add SppPcap class ogawa.yasufumi
2019-02-10 3:08 ` [spp] [PATCH v3 7/9] controller: add pcap command to SPP controller ogawa.yasufumi
2019-02-10 3:08 ` [spp] [PATCH v3 8/9] controlle: refactor pcap command ogawa.yasufumi
2019-02-10 3:08 ` [spp] [PATCH v3 9/9] controller: fix init of pcap instances ogawa.yasufumi
2019-02-13 5:55 ` Yasufumi Ogawa [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=b344b68d-75cb-4f02-1f21-e28c87cd904e@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
--cc=x-fn-spp@sl.ntt-tx.co.jp \
/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).