From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 0/2] Fix compile errors of ring latency stats
Date: Mon, 1 Jul 2019 13:12:09 +0900 [thread overview]
Message-ID: <20190701041211.34060-1-yasufum.o@gmail.com> (raw)
From: Yasufumi Ogawa <yasufum.o@gmail.com>
For adding burst functions and changing dir structure, it causes compile
errors if CFLAG DSPP_RINGLATENCYSTATS_ENABLE is activated in each of
Makefiles. This update is to fix this issue.
Yasufumi Ogawa (2):
shared/sec: fix compile error of ringlatencystats
shared/sec: remove source and header of spp_port
src/mirror/Makefile | 1 -
src/mirror/spp_mirror.c | 37 +++++++--
src/pcap/Makefile | 1 -
src/pcap/spp_pcap.c | 13 ++-
.../spp_worker_th/cmd_res_formatter.c | 1 -
.../secondary/spp_worker_th/cmd_runner.c | 1 -
.../secondary/spp_worker_th/cmd_utils.c | 41 ----------
.../secondary/spp_worker_th/cmd_utils.h | 5 --
.../secondary/spp_worker_th/port_capability.c | 60 ++++++++++----
.../secondary/spp_worker_th/port_capability.h | 4 +-
.../spp_worker_th/ringlatencystats.c | 81 +++++++++++++++++++
.../spp_worker_th/ringlatencystats.h | 65 +++++++++++++++
src/shared/secondary/spp_worker_th/spp_port.c | 57 -------------
src/shared/secondary/spp_worker_th/spp_port.h | 34 --------
src/vf/Makefile | 2 +-
src/vf/classifier_mac.c | 16 ++++
src/vf/forwarder.c | 18 ++++-
src/vf/spp_vf.c | 9 ++-
18 files changed, 272 insertions(+), 174 deletions(-)
delete mode 100644 src/shared/secondary/spp_worker_th/spp_port.c
delete mode 100644 src/shared/secondary/spp_worker_th/spp_port.h
--
2.17.1
next reply other threads:[~2019-07-01 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 4:12 yasufum.o [this message]
2019-07-01 4:12 ` [spp] [PATCH 1/2] shared/sec: fix compile error of ringlatencystats yasufum.o
2019-07-01 4:12 ` [spp] [PATCH 2/2] shared/sec: remove source and header of spp_port yasufum.o
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=20190701041211.34060-1-yasufum.o@gmail.com \
--to=yasufum.o@gmail.com \
--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).