From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 0/6] Update for spp_pcap
Date: Thu, 14 Feb 2019 11:47:20 +0900 [thread overview]
Message-ID: <20190214024726.40861-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
This series of patches is to add spp_pcap support, update GNUmakefile
and for SPP CLI and refactor spp_pcap's options. It also includes
refactoring for the name of functions and variables.
Yasufumi Ogawa (6):
spp_pcap: refactor app options
spp-ctl: update spp_pcap opts for validation
controller: remove local default config
controller: add pcap support for pri completion
spp_pcap: refactor name of funcs and vars
makefile: update dist-clean task
GNUmakefile | 3 +
src/controller/commands/pri.py | 42 ++++----------
src/controller/config/default.yml | 3 +
src/pcap/spp_pcap.c | 91 +++++++++++++++----------------
src/pcap/spp_proc.h | 6 +-
src/spp-ctl/spp_proc.py | 13 +++--
6 files changed, 70 insertions(+), 88 deletions(-)
--
2.17.1
next reply other threads:[~2019-02-14 2:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 2:47 ogawa.yasufumi [this message]
2019-02-14 2:47 ` [spp] [PATCH 1/6] spp_pcap: refactor app options ogawa.yasufumi
2019-02-14 2:47 ` [spp] [PATCH 2/6] spp-ctl: update spp_pcap opts for validation ogawa.yasufumi
2019-02-14 2:47 ` [spp] [PATCH 3/6] controller: remove local default config ogawa.yasufumi
2019-02-14 2:47 ` [spp] [PATCH 4/6] controller: add pcap support for pri completion ogawa.yasufumi
2019-02-14 2:47 ` [spp] [PATCH 5/6] spp_pcap: refactor name of funcs and vars ogawa.yasufumi
2019-02-14 2:47 ` [spp] [PATCH 6/6] makefile: update dist-clean task ogawa.yasufumi
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=20190214024726.40861-1-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).