From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 0/4] Add specific RX and TX burst functions
Date: Mon, 1 Jul 2019 13:11:22 +0900 [thread overview]
Message-ID: <20190701041126.33947-1-yasufum.o@gmail.com> (raw)
From: Yasufumi Ogawa <yasufum.o@gmail.com>
In SPP worker processes, customized version of rte_eth_rx_burst() and
rte_eth_tx_burst() are defined to add features of VLAN or ring lantency
statistics. However, these features are not required from all of
processes.
This series of patches is to add burst functions used for VLAN,
statistics or both.
Yasufumi Ogawa (4):
shared/sec: Add RX and TX burst without VLAN
spp_vf: change to use burst funcs with VLAN
spp_mirror: change to use burst funcs with VLAN
spp_pcap: update include path of port capability
src/mirror/Makefile | 1 +
src/mirror/mir_cmd_runner.c | 1 +
src/mirror/spp_mirror.c | 7 +-
src/pcap/Makefile | 1 +
src/pcap/spp_pcap.c | 4 +-
.../spp_worker_th/cmd_res_formatter.c | 2 +
.../spp_worker_th/cmd_res_formatter.h | 1 -
.../secondary/spp_worker_th/port_capability.c | 409 ++++++++++++++++++
.../secondary/spp_worker_th/port_capability.h | 84 ++++
src/shared/secondary/spp_worker_th/spp_port.c | 373 +---------------
src/shared/secondary/spp_worker_th/spp_port.h | 100 +----
src/vf/Makefile | 2 +-
src/vf/classifier_mac.c | 8 +-
src/vf/forwarder.c | 5 +-
src/vf/spp_vf.c | 1 +
src/vf/vf_cmd_runner.c | 1 +
16 files changed, 546 insertions(+), 454 deletions(-)
create mode 100644 src/shared/secondary/spp_worker_th/port_capability.c
create mode 100644 src/shared/secondary/spp_worker_th/port_capability.h
--
2.17.1
next reply other threads:[~2019-07-01 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 4:11 yasufum.o [this message]
2019-07-01 4:11 ` [spp] [PATCH 1/4] shared/sec: Add RX and TX burst without VLAN yasufum.o
2019-07-01 4:11 ` [spp] [PATCH 2/4] spp_vf: change to use burst funcs with VLAN yasufum.o
2019-07-01 4:11 ` [spp] [PATCH 3/4] spp_mirror: " yasufum.o
2019-07-01 4:11 ` [spp] [PATCH 4/4] spp_pcap: update include path of port capability 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=20190701041126.33947-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).